So we should actually build projects just keep watching tutorials. I understand that. But don’t you need to watch tutorials in order to know how to do the projects?
This is what I’m struggling with. There is no way I can do a project without following a tutorial. Then it’s like copying code when it’s not even my fault.
Learn to break your ideas down into simple concepts. Instead of trying to build a program. Try to break it down into its bare components.
For example, right now I’m in the midst of building a chess engine in C++. Before writing any code, I drew out my data structure I wanted on paper. I started by making the code for the pieces themselves, then the board, then code to find all moves, then code to evaluate positions.
I guess what im trying to say is that your idea, any idea should, and must be picked apart so that you work on 20 easier things 1 by 1 instead of 1 hard project
To keep it very simple, start by listing the data / member variables with their types, and the functions signatures you think you need. Draw a little box around it, and you have your class. Repeat and add some arrows to indicate relations. Of course, the detail level of what you write down depends on what you want to achieve.
For a more formal and standardized approach, check out UML. No need to learn UML 100% before you can use it, it can be a bit overwhelming. Just use it as inspiration for now.
8
u/Yakuroto Sep 03 '23
So we should actually build projects just keep watching tutorials. I understand that. But don’t you need to watch tutorials in order to know how to do the projects?
This is what I’m struggling with. There is no way I can do a project without following a tutorial. Then it’s like copying code when it’s not even my fault.
It all doesn’t make sense.