Re:Goodbye, Clean Code
by humanrebar on Sunday January 12, 2020 @07:54AM
(#22026075)
Even for static business purposes, the target environment changes over time. The OS gets upgraded, security bugs are discovered, dependencies become end-of-life'd, language runtimes are replaced, etc.
Re:Goodbye, Clean Code
by jhoutromundo on Sunday January 12, 2020 @12:14PM
(#22027442)
I think implementing new features isn't the same as maintence. Maintennce is to make something that isn't working work.
Disagree. Your code should reflect the business you're in, and changes to the business are what creates opportunity and let you turn your skills into profit.
Clean code is absolutely a means to an end, and if you've got a codebase that's just sitting there fulfilling some static business purpose then yes, it makes sense to leave it ugly. (Similarly with code that you know is being end-of-lifed soon - if there is not going to be a need to make changes to the code in the future then it's fine to load it up with technical debt until it sinks). But that's the exception rather than the rule.