So who's this article for, exactly?
"All of a sudden you start realizing that writing code is more than just attempting to solve a problem; it is attempting to solve a problem for your user. The ability to recognize that you are building for users gives you more perspective and clarity."
Not to be that guy, but for anyone who codes for a living this is.. kinda obvious. In fact it's often formally codified into business practices, particularly in any form of Agile software development.
At this point I thought he was talking to researchers, which might make some sense (God knows some of my professors' code wouldn't pass a basic code review), but then he goes on to talk about teams and designers and animosity between developers and designers... huh?
If there's animosity between a company's developers and designers then one or more people are putting their egos ahead of their jobs. Granted there are bad apples in every barrel, but it's a behavioral problem, not a technical one. Certainly not one that's going to be solved by taking up a hobby.
So I guess this column is aimed at imparting basic insight known by many Computer Science undergrads to mediocre software developers working at mediocre companies. Fair enough, but I doubt those types of people read HN.