> What bothers me most about this is the idea that programmers are some kind of underclass that just doesn't get "normal" people. The truth is that we're people too who have a lot of the same needs as "normal" people.
I think the author was simply trying to articulate a rift that sometimes occurs between a party with a (perceived or actual) problem and the party with solutions for that problem. According to his barbershop example, that problem/solution rift is the result of a fundamental misunderstanding of the problem statement. If I could abstract the article in one sentence, I would say, "If you are trying to solve a problem that you yourself do not have, make sure you actually understand the problem from the perspective of the party you are solving it for before you go building things."
The author may have gone a bit far in generalizing programmers/engineers, but would you agree it is fair to say that it is easy enough for _anyone_ to fall into the aforementioned trap if they are not conscious of it?
An occurring theme I have noticed while speaking with people (not just engineers and/or programmers) is that we have a tendency to project ourselves on other people. I don't think that is a bad thing in moderation (that's a different matter of discourse), but I have had at least two different conversations with entrepreneurs where they simply could not for the life of them understand why someone would rather "just get a job working for someone else" than start their own company. It simply does not register in their world view that someone does not share their way of thinking. My anecdote is tangential at best, but my point is that the object of the article is not to diminish programmers. Rather, it is to elevate the perspective of those subject to a certain myopia that they would otherwise not think to confront.