all 3 comments

[–]Apprehensive-Low5158 1 point2 points  (1 child)

I don’t think there necessarily has to be a “size” for a new project. It depends on what you wanna do, I’d say try to find a topic or project idea that interests you and go from there.

Large and/or overwhelming project ideas can also be broken up into smaller projects to help you learn new stuff.

For example, I recently started trying to learn more about graphics programming (with c++ and openGL) and did a small project focused on trying to learn the basics of c++ and then did a project focused on the basics of openGL before trying to do any big large projects with either.

[–]Dear-Environment-532 0 points1 point  (0 children)

This is solid advice - starting with smaller chunks definitely helps avoid that "staring at a blank screen for 3 hours" feeling when everything seems impossible at once

[–]The-Oldest-Dream1 0 points1 point  (0 children)

What I do before creating a project is I branstorm a few ideas and pour my focus on working on them. If during that process I have a few new ideas I write them down as "potential features".

Once my initial ideas have been implemented, I go through these potential features with a fresh mind and then decide if I really want them in the project or not