> The conversation you have is "Boss, I can crank this out quickly but the faster its written the more likely it will have some future problem in it."

Not entirely sure if this is satire or not but it's a genuine conversation that I've had with a few clients.

I call it "the spectrum of quality" conversation. I can write beautiful unit tested code that will not explode unexpectedly at 3am on a Sunday several years later...but it won't be (relatively) quick to get there.

Alternatively, I can rush through something that will have to be rewritten later and it'll only take me a few hours. Part of me dies writing that type of code but there's a time and a place for it.

You want to hit the afterburner? No problem, but there are consequences.