That's funny and sadly true in many cases. But come on, I think we all know what point the article is really trying to make: You can run off and start writing

That's funny and sadly true in many cases. But come on, I think we all know what point the article is really trying to make: You can run off and start writing code to some spec in your head; or you can spend a little time upfront finding out what the business needs and users' needs are before hitting the keyboard. It's not really about putting down "hackers" or lifting up corporate developers. It's about the approach you take when you're building an application that solves a given business or user problem. When you're writing code for someone else, it makes sense to ask questions, lest you create something that doesn't actually meet the person's needs. When you're experimenting or just writing code for yourself, by all means just hacking away sometimes makes the most sense.