I don't think I know of a single good programmer that learned to code in such a horrible grueling manner. If you're not making shit from the very beginning, then you're never going to learn to love it, and if you don't love it, then you're not going to be very good at it.
One of the most important traits of a good programmer is that while they work hard, they barely consider it work. Especially at the beginning, where the work:play ratio is practically zero. The boring programming grind should only start when you're doing work for other people that you don't care very much about; if it feels like that before you reach that stage, you're doing something wrong. Find a nice easy graphical language to play around with while you learn about functions, classes, I/O, and algorithms; you can start worrying about mastering the LAMP stack once you've realized that the programming part of it is easy and fun, and the LAMP part of it is just another set of technologies whose quirks we learn and put up with in the name of getting things done a bit more easily.
I think the real problem is that the blog post might be right: you do need to know the basics to get very far in programming. But the basics of programming have nothing to do with hard library-specific study and grueling memorization; they involve loving to build things and make them work, thinking logically and experimenting with all sorts of code just to see what happens. The rest comes pretty naturally once you have that down.