3 ms·
In the same way that it can be difficult to justify spending a week to reduce technical debt within a fast-moving engineering team, I think there's a parallel c
by jka 5y ago
In the same way that it can be difficult to justify spending a week to reduce technical debt within a fast-moving engineering team, I think there's a parallel challenge for industry to make the work of maintenance be seen -- and be rewarded -- equally alongside feature development.
Perhaps we already have (or at least nearly have) enough code, systems and services to achieve the tasks that 97.5% of us need, but they're all broken and non-interoperable in frustrating ways.
Can we spend a while honing and refining those before building incompatible replacements? Or, failing that, at least identify the core issues before repeating the same mistakes?
- Aeolun 5y agoNot sure what systems you are trying to hone?
- jka 5y agoDesktop environments, operating systems, communication and collaboration tools, web browsers, widely-used shared libraries, for example.. there are a large number of software systems that people rely on where stability, performance, bugfixes and compatibility improvements are worthy goals.
- cat199 5y agothis highlights the fact that we often try to solve wetware problems with software, because software is "easier". so long as people don't want to look at their own 'stuff', this mis-attribution in requirements will always be an issue.