What's next?
So i just finished my c++ book,and i'm wondering what do i do next?
Everyone says i should get another book,but they're all pretty much the same.
I'm pretty lost here, what do you do next,i'm wondering how do you learn all that stuff.I mean i want to make serious programs which actually look like something.I want to add life into my programming, so i want to know how can i learn adding graphics to my programs,how to take advantage of all the stuff.If anyone could help me i would be very,very tankful.
:)
Everyone says i should get another book,but they're all pretty much the same.
I'm pretty lost here, what do you do next,i'm wondering how do you learn all that stuff.I mean i want to make serious programs which actually look like something.I want to add life into my programming, so i want to know how can i learn adding graphics to my programs,how to take advantage of all the stuff.If anyone could help me i would be very,very tankful.
:)
Think of C++ as merely a tool (because it is). If you're not making or fixing anything, tools are pretty much useless, therefore, the first step is to define an objective. What do you want to make?
The way you use your computer may be a well of ideas. There may be something you do every day that can be automated, or a very specific function you can't find anywhere.
Once you've done that, the second step is to figure out the requirements to reach that goal. How long will it take? Do I need to learn anything new? Are there any libraries available that can simplify my job? Has anyone ever done something even remotely similar to what what I'm trying to do? That last one underlined because it may be better to modify existing code than starting from scratch.
Not everything will survive this phase. Sometimes you'll realize that the costs far outweigh the benefits and scrap the idea. That's okay, because that's partly the point of this step. Starting a project and realize two months later that you're stuck because you bit more than you can chew is bad planning.
I think I had more to say, but I can't remember what it was and I'm starving, so if anyone wants to complete my thought, go right ahead.
The way you use your computer may be a well of ideas. There may be something you do every day that can be automated, or a very specific function you can't find anywhere.
Once you've done that, the second step is to figure out the requirements to reach that goal. How long will it take? Do I need to learn anything new? Are there any libraries available that can simplify my job? Has anyone ever done something even remotely similar to what what I'm trying to do? That last one underlined because it may be better to modify existing code than starting from scratch.
Not everything will survive this phase. Sometimes you'll realize that the costs far outweigh the benefits and scrap the idea. That's okay, because that's partly the point of this step. Starting a project and realize two months later that you're stuck because you bit more than you can chew is bad planning.
I think I had more to say, but I can't remember what it was and I'm starving, so if anyone wants to complete my thought, go right ahead.
Topic archived. No new replies allowed.