Re:We invested 10% to pay back tech debt; Here's what happened
by moris_borris on Sunday January 15, 2023 @09:27PM
(#34396086)
The miracle of a clean code base is that it means some programmers got together and agreed on a bunch of things.
Re:We invested 10% to pay back tech debt; Here's what happened
by tatersolid on Tuesday January 17, 2023 @10:36AM
(#34413719)
I’d think it’s the opposite: clean code indicates 1-2 opinionated individuals built it. Committee decisions are almost always overly complex compromises with too many special cases. See most RFCs, IEEE specs, congressional bills.
If the answer is “No”, it can be difficult for others to understand. Reworking that code to follow our architecture generally makes it easier for us all to follow.
One might need to not follow the architecture because it doesn’t handle something new to the app. When that happens, we try, first, to update the architecture to be able to handle the requirement and then implement the feature. But if that isn’t possible, we plan to clean up the debt as soon as we can after shipping.
Overall, it has worked remarkably well for our team and has led to what I consider the “cleanest” code base I have ever worked on. But it is dependent upon us having a shared understanding of how we implement features.