1. When you just start out, doing 'hello world'-tier exercises. At this point you think learning the language's syntax/semantics is the hardest part about programming. People stuck at this stage think that 'everyone can code', and think a good programmer is one that can code in the most languages.
2. You focus on actual function of your programs. Now you view programming languages as tools to get the job done.
3. You realize that "real" programming is not so much about 'what' your program can do, but rather 'how well' it can do it. Your work is less about big picture ideas and more about the specifics. Optimization, scaleability, etc become the focus of your code. You also spend more of your time keeping up with different platforms and frameworks.
stage 1. I'm an intro to CS student and I understand nothing that's happening ;__;
Connor King
I disagree, I think the Dreyfus model better explains skill levels and mindsets in programming.
Christian Baker
4. You have a job. You realize that real programming is not so much about what your program can do, but how well you can explain and document it. It is expected that your program works too spec. You spend most of your time socializing with your co-workers because you aren't a loser
Ayden Lopez
everyone on Jow Forums is at stage 1, most people here would debate the fact that stage 3 even exists and thinks the quality of a programmer is determined by how good they are at writing algorithims
Easton Hernandez
>be woman >take programming 101 class >90k starting
Leo Collins
you're a dead-end code monkey
Christian Turner
5. You are a project manager. You realize that you no longer have to program and thus real programming is no longer your concern. You win.
Luis Harris
You forgot to add a github link to your account frend.
Grayson Green
In between stage 2 and 3, honestly. Most people out of college should be at stage 2, and slowly transition to stage 3 in their first years of real work in the field.
