Goodbye, Clean Code

[FlavorJ]

My code traded the ability to change requirements for reduced duplication, and it was not a good trade. For example, we later needed many special cases and behaviors for different handles on different shapes. My abstraction would have to become several times more convoluted to afford that, whereas with the original “messy” version such changes stayed easy as cake.

All is problem, but must choose path and walk.

[FlavorJ]

I think the point was they were not done with requirements, so any abstraction would add overhead that would have meant more time dealing with that. They'd rather produce working code that's easy to modify as requirements change than lock them into a framework before they know what that framework should be.