Perhaps less useful is the author extrapolating from his community college classmates to the general programmer population.
But the part I disagree with is the reductionist description of programmers as people who only type and solve problems. This is only true if you expand the definition of "problem" to be so broad that it's meaningless. As a good software developer, you have to make aesthetic choices, exhibit empathy with customers and coworkers, do boring paperwork, be personable, and many other things. I'm not sure all of these things are problem solving.
I also don't think any of his 8 pithy statements of advice are very helpful. Just one example: "Take everything very seriously." Really? Is this tongue-in-cheek? How about, "Don't take yourself so seriously. Have fun and be curious about your world." That sounds like better advice to potential programmers to me.