One can be a professional artist as well as a professional engineer. I prefer the former generating visualizations and the latter doing operating systems. But I really want the #!~!&@$~! to work.
I have absolutely ZERO experience with slap-it-together code coming frompeople who think programming is an art form.
All, and I repeat my n=1 anecdote at the top of my voice, ALL, of the shit code I have seen was written by people who viewed programming as a profession, namely something to be done for money using processes that valued delivery over quality.
Which is not to say that other programmers who view themselves as professionals have not written terrific code. But I vigorously dispute the notion that there is a correlation between slap-it-together fecality and someone's self-images as an artist.
Meanwhile, the rest of us will continue to have fun with software that does amazing stuff and sometimes breaks.
There's a not-so-old saying: "Brilliant people are often hard to work with, but if I've got to choose between working with a brilliant person that is hard to work with, or a stupid person that is easy to work with, I'll always choose the former."
The same is true of software. When you're pushing the envelope, things break. Learn to live with it, or stop bothering with computers until those of us who are more passionate about doing extraordinary things have left the field. We should be done in about 50 years.
Note: this is not a defense of cowboy programming. It's a defense of genius cowboy programming. If someone like Linus Torvalds, as an amateur student programmer, wants to write something as awesome as Linux, who are you to suggest that he shouldn't?
When Linus did his groundbreaking work, that was pure creativity. Redhat, however, better be a little more grounded.
You need the "artists", i.e. the extraordinary, unprofessional people who do something crazy that no professional would ever attempt, and come up with something that pushes the envelope in new and unexpected ways.
And you need the "engineers", the professionals who will convert that (or other things) into something steady, reliable, rock-solid.
I don't think that your rephrasing helped, personally. It made a point which was in agreement with the article look like it was a disagreement.
This, perhaps, is most true in those who term themselves user interface developers. They probably started with HTML and CSS, and started learning Javascript from snippets pasted across the net in the early 00's. Unfortunately, most never took the time to actually learn the language, so these days they just slap together jQuery plugins and call it a day... crossing their fingers that it works, and having no idea what to do -- other than an ugly hack. Like user agent sniffing (something about jQuery not being fully compatible with IE6. If you've run into these issues, you know what I mean. Prototype is even worse -- hell, it doesn't realize that you can actually determine what the rendered CSS of an element is...).
Do we always have time to do this? No. Is it always appropriate to do this? No. But when it is mission critical work, deliver the goods.