How long does it take to become a real c++ programmer
it takes about 12 months to study a good book. But after that - can someone claim to be a programmer? What do you do then?
It depends on what you mean by "real programmer"
Anyway, spending time in reading books is a good thing but the best knowledge comes with practice: if you try each time you finish a program a more challenging one over and over you can learn in a really short time lots of thing, even advanced stuff.
Anyway, spending time in reading books is a good thing but the best knowledge comes with practice: if you try each time you finish a program a more challenging one over and over you can learn in a really short time lots of thing, even advanced stuff.
Last edited on
You aren't a real programmer until you start thinking in code.
Just kidding. The truth is, you aren't a real programmer until you start dreaming in code.
Just kidding. The truth is, you aren't a real programmer until you start dreaming in code.
Are we talking about a real programmer or a Real Programmer?
Anyway, I'd say it's possible to achieve proficiency (i.e. enough skill to be able to do anything useful) in around 18 months given adequate conditions. Having an Internet connection and a strong computer are important factors. When you hit a dead end it's important not wasting time moving to look information up, and it's also important to waste as little time compiling as possible. When you're a beginner, you'll compile many times, and if each compilation takes too long, that's a direct reduction on the amount of work you can get done in a single sitting.
Anyway, I'd say it's possible to achieve proficiency (i.e. enough skill to be able to do anything useful) in around 18 months given adequate conditions. Having an Internet connection and a strong computer are important factors. When you hit a dead end it's important not wasting time moving to look information up, and it's also important to waste as little time compiling as possible. When you're a beginner, you'll compile many times, and if each compilation takes too long, that's a direct reduction on the amount of work you can get done in a single sitting.
Everyone should understand the difference between a real programmer and a Real Programmer!
The modern explanation: "Real Programmers use butterflies". http://xkcd.com/378/
This is a story of a Real Programmer told 25 years ago, about a still earlier time. http://catb.org/jargon/html/story-of-mel.html
The modern explanation: "Real Programmers use butterflies". http://xkcd.com/378/
This is a story of a Real Programmer told 25 years ago, about a still earlier time. http://catb.org/jargon/html/story-of-mel.html
| Since Mel knew the numerical value of every operation code, and assigned his own drum addresses, every instruction he wrote could also be considered a numerical constant. He could pick up an earlier “add” instruction, say, and multiply by it, if it had the right numeric value. His code was not easy for someone else to modify. |
Last edited on
A writer writes. You can't learn to program by reading, but only by writing, testing, and debugging.
There's so much more to software development than writing code that works. Proficiency in the language is the first step. Make sure you learn the debugger while you learn the language. Make sure you really understand pointers, recursion, and exception handling. Those three areas often stump self-taught programmers, and they aren't easy.
Take the time to regularly look at the object code (disassembly) in the debugger - you don't need to learn how to program in assembly in order to program in C++, but you need to be able to read the sort of assembly that the compiler normally generates, so that you can get past points where you're sure the code is right, but it does the wrong thing. If you look at this regularly when debugging, you'll pick it up naturally.
There's so much more to software development than writing code that works. Proficiency in the language is the first step. Make sure you learn the debugger while you learn the language. Make sure you really understand pointers, recursion, and exception handling. Those three areas often stump self-taught programmers, and they aren't easy.
Take the time to regularly look at the object code (disassembly) in the debugger - you don't need to learn how to program in assembly in order to program in C++, but you need to be able to read the sort of assembly that the compiler normally generates, so that you can get past points where you're sure the code is right, but it does the wrong thing. If you look at this regularly when debugging, you'll pick it up naturally.
Becoming proficient requires guidance. Guidance can be found in many places; a book may be all you need. Your success in learning is, and always will be, all on you.
My point is that you can code by yourself for years and make little progress; efficient practices/methodologies/algorithms have all come from collective contributions to the field--not just 'some smart guy' but large-scale successes and failures that may be used as examples from which to learn. Learn the right practices and you could be proficient in no time.
My point is that you can code by yourself for years and make little progress; efficient practices/methodologies/algorithms have all come from collective contributions to the field--not just 'some smart guy' but large-scale successes and failures that may be used as examples from which to learn. Learn the right practices and you could be proficient in no time.
Last edited on
Topic archived. No new replies allowed.