Elsewhere in this discussion, I described my first Flux experience. In that same job, the boss decided (after we switched to a pseudo-Flux, Frankenstein's mons

Elsewhere in this discussion, I described my first Flux experience. In that same job, the boss decided (after we switched to a pseudo-Flux, Frankenstein's monster of MVC component libs that slowed development to an excruciating crawl) to bring in a consultant to "help". He was the "crap out apparently-working code quickly" brand of "10x Programmer". Some basic functionality for new features got added in a hurry, over a couple weeks' time. The following couple weeks were dedicated to fixing everything he wrote. Yes, I agree: "grown up" programmers think beyond what seems to work right now. Sure, I use dirty hacks semi-regularly, but only when I'm first feeling out how something works. It doesn't last more than a couple hours, usually far less, because the point isn't to commit that code but to learn how to think about the problem so I can do it right, and a "done right" rewrite takes less time to get working than the initial dirty hack. The "done right" rewrite also doesn't impose tremendous maintenance and continuing development costs over months to come the way the dirty hack would. If the author means real programmers use dirty hacks to figure out what they're doing, then they make it right, that's fine. If not, that's not fine at all.