What is not clear to me is what the author has been doing for a living during these last few years. I can remember getting started doing web development way ba

What is not clear to me is what the author has been doing for a living during these last few years. I can remember getting started doing web development way back in the Perl/CGI days, before JavaScript libraries and massive web frameworks were common, and I can remember getting overwhelmed even then. I can remember trying to learn OO first in Perl and quitting before coming back to it from another language a year later. Point is, programming is hard, but to me "being a programmer" means being a programmer as a job, where a) you have to solve problems for a living and b) you don't get to quit. Where I feel the author is screwing herself is the endless stream of tutorials, coupled with drinking from the firehose. The language and the frameworks are two different problems that must be tackled, I think, in two different ways. For example, when learning to code for iOS, it's not Objective-C that gets you, it's the new environment, frameworks and libraries. However, you don't get to quit and say, "I could have done this in Wordpress." I'm rambling. Point? Get a job as a programmer, paint yourself into that corner and stay there. It has been said earlier, and I agree: commit to one language/framework. Learn it really well. THEN, and this is after 5 years or so, language hop all you want with a more robust understanding of programming in general.