4 ms·
You’re already doing what is probably the overwhelmingly most common practice (that is among teams who even think about the topic): > just budget a proportion
by sokoloff 5y ago
You’re already doing what is probably the overwhelmingly most common practice (that is among teams who even think about the topic):
> just budget a proportion of each quarter to address technical debt and unexpected bug reports, but are finding this proportion is getting increasingly taxed by the growing feature set
For any given feature, it’s a matter of judgment how to build it, but I suspect that most companies would way rather live with “we make reasonable calls as we go” with regards to maintaining software than to have any false precision around exactly how much this new thing will cost if built as A, built as B, or not built. The error bars are just too large I think.
Modeling increasing overall absolute maintenance costs as your codebase and tech footprint expand is fairly easy and gets you pretty close for the next 12 months.