I'm very disappointed that he starts out with a diagram and "This is what ugly code looks like.", but doesn't follow it up with "This is what beautiful code looks like."<p>Then again, maybe that part's just in the book this excerpt is trying to sell.
I enjoyed reading this article. Especially at the end. A 2015 programmers is a much different beast of a 1990 programmer.<p>Not better or worst, but because of how fast things move this days we must be "eclectic" regarding out tools, and shape-shifters from new frameworks that pop-out every week.<p>This is specially true in the JS world.
The author is of course absolutly correct in every respect but I can't help thinking that he's is one of those devs who struggles terribly with programming. This type tends to give up eventually. Sometimes after years of work. His struggle to learn git is telling. Sure git is complex but it's not quite that hard for many of us. This leads to bewildered frustration with programming and a general distrust of all programs.
Interesting article... but maybe the author should have taken a cue from programming and refactored/edited it to be more clear, concise and structured.<p>I found it a bit rambling without clear premise or pay off. He sounds like someone who talks about programming from the outside while never having been deeply immersed in it himself.<p>Clarity of writing follows clarity of thought.