[distracted828]

Here is something I don't understand: How does one effectively deliver on a project while writing crappy code? Doesn't trying to do that result in the codebase becoming so confusing that you don't know how to add things to it without breaking other things?

[scarmig]

You write crappy code to meet unrealistic deadlines, you get promoted, hand off shitty code to someone else who is viewed as a low performer because they were too busy writing good code.

It's not actually that clear cut (it's more like an average performers who write shitty code quickly will be rewarded over an average performer writing solid code less quickly), but code quality isn't legible to management and HR, who control resource allocation. Even a line manager knowledgeable about the code base has incentives to lead a team that produces shitty code now instead of good code later.

[Mikerad1979]

When writing crappy code you are either not thinking long term at all, or you are just "kicking the can down the road", in that you'll pay for it later when there isn't a time crunch.

Not that I've ever done something like that...

[distracted828]

What I mean is, how do you keep it from catching up with you a week later?

[st3v3r]

Bah. That's later on. Right now, we're delivering at a speedy pace. The time we save now can be used later. Hell, I might not even be here later, so I won't have to care.