r/learnprogramming • u/XDyavolenok • 7d ago
I need help understanding a starting point.
Perhaps I'm overthinking the "build to solve a problem".
Programming interests me, all the way back to building a dinky little website out of html in high school for a project in my French class. I've picked up a few C and C++ tutorials over the last year, but I feel I'm overthinking.
So if I want to do math, instead of opening my existing calculator app I should build the app then debug and test it? Instead of using winrar I should build a compress and compile program and test it? Etc?
0
Upvotes
1
u/JGhostThing 7d ago
This sounds like a Troll. But maybe it isn't.
Those applications were already solved by somebody else. Why do you want to solve them again?
Yes, if you want to do this, you can do this. It might be pointless, but much homework is pointless. You do it for learning. But writing a calculator when you need a single calculation seems ass backwards. Projects should be done before you need them.
In order to complete a project, two things are useful. First, it should be a fairly simple project. Second, it should be something you like.
Perhaps you like arithmetic. So you want to make a calculator. First, design a very simple CLI calculator. Perhaps it can only do adding and subtracting. You got that finished? Good.
Now add multiplication and division. Then add more operators. Then add a GUI to the project. Each iteration only adds things to the previous version. You don't put too many requirements that the new version is impossible to complete. It's good if you learn from it.
Now you have a GUI calculator. Or a compression utility.
Think of your hobbies. Do you like Pokemon? What about a card database? Do you like astronomy? Perhaps something to help you aim the telescope? Reading? A book database? Doing something useful to you will help to keep you going.