How often have you written a piece of code and known ahead of time that you'd never have to touch it again? Even throw-away code, like data migrations, often ge

How often have you written a piece of code and known ahead of time that you'd never have to touch it again? Even throw-away code, like data migrations, often gets revisited several times while you're writing it. So why is your supposedly decent programmer writing crappy code and assuming that they'll never have to touch it again? Which is my original point. Traditionally the expectation is crappy-fast-and-cheap vs. perfect-slow-and-expensive, but that rarely holds. Instead it's usually the crappy code that ends up being slow to write and expensive, stuck in endless code and bugfix cycles trying to get it right.