6 ms·
You can certainly be a programmer in 12 weeks, but you will be different programmer than what we are expecting here. You can also learn programming by reading
by kamaal 15y ago
You can certainly be a programmer in 12 weeks, but you will be different programmer than what we are expecting here.
You can also learn programming by reading 'Learn programming in 30 days'. But that is a very different kind of programming than what most people are expecting in this thread. You can learn enough programming to begin to understand how to work with software. It gives you a start. It also works if your job is extremely trivial. And I think the target audience for the book is those kind of people.
Coming to programming as a profession, in that case there are a lot of aspects that influence your full time profession, among that is giving your full learning every detail of programming and related ecosystem. Other aspects are productivity, management, analytical skills, UI design, requirements gathering, people skills. Also there are many other things required to win in practical software environments like working under tough deadlines, learning to deal with frequent stress and burnout. Keeping in touch with rapidly changing tech scenario, tools and languages. The list goes endless. I haven't covered even a percent of what I wanted to write.
Your regular data structure and algorithm sauce is probably 1% of what is required to win in practical software development today. There are 99% of other things which are not taught in books, colleges and universities. You have to learn them through experience, by working.
So just in case you think you have spent 10 years learning all the secret recipes in computer science books but are not good in other areas. You are no better than the 'Learn programming in 30 days guy'. Because if has problems in a set of areas, you have equal number of problem with another equivalent set.
This is something I have seen among so many bright, people with great academics, who don't make it big in the industry. They just don't understand so many practical aspects of the industry. Just like how 12 weeks programming guy doesn't understand all aspects of practical programming.
- prophetjohn 15y agoI get the point of this post, even if it seems a bit of a tangent from the what the author is saying, but >>in case you think you have spent 10 years learning all the secret recipes in computer science books but are not good in other areas. You are no better than the 'Learn programming in 30 days guy'. and >>Your regular data structure and algorithm sauce is probably 1% of what is required is just false. Sure, studying classical CS concepts is not all there is to software development and success in the software development industry, but your comment largely renders advanced degrees, like PhDs, about as useful as some poorly written Java book with regard to success as a software engineer.
- kamaal 15y ago>>but your comment largely renders advanced degrees, like PhDs, about as useful as some poorly written Java book with regard to success as a software engineer. I am not saying that at all. All I'm saying is, as programmers we tend to assume knowledge of text books and programming is all that is needed to win. And that if you have it, that is all there is that it takes to win. This is largely untrue. I have seen that this is hardly what it takes. It's important to learn the fundamental and concepts, but if you are bad at everything else. In the the practical scenario you and the 12 weeks programming guy will both sail in the same boat. You will be bad at one set of things, and he will be bad at the other.
- prophetjohn 15y agoTextbook-type knowledge of programming (and more specifically, data structures and algorithms) are not all that's required to be successful in this industry, but it's sure a hell of a lot more important than 1% of the whole puzzle. I can't say much about 12-weeks-programmer guy, but if the only skill that 12-weeks-programmer guy has is the programming skills he's obtained in those 12 weeks and the only skills 10-years-of-pounding-CS-books guy has are the skills he's obtained from those books, I'm going to pick the guys that's been reading all about automata theory to be more successful. Not that I'm saying that the author is destined to be unsuccessful. I'm just trying to point out that classical CS skills are more important than you're portraying.
- kamaal 15y agoI would do the same. But if I find 12 weeks guy to be more productive than the CS guy. I will be hiring the 12 weeks guy not the CS guy. I'm hiring people for getting stuff done. Not just because they know something.
- karamazov 15y agoNo where in his post did he claim to understand all aspects of programming. This guy spent 12 weeks learning the basics, and is now working as a full-time programmer - presumably this is the road to "learn[ing] through experience, by working".
- mseebach 15y agoWho are these "we" who has such well defined expectations of what kinds of programmers are allowed to participate here? The guy sets a goal, works hard to achieve it, and succeeds. Win. More power to him. In fact I rather envy his ability to focus. He's not even approaching a claim to understanding all the practical aspects of the industry or programming. He is humble and thirsty for more knowledge. He is a beginner, and if you look closely, I think you'll find that we've all been beginners.