3 ms·
Process debt is another one I've invariably come across and covers the need for loose requirements (especially early on). There's a lot of technical debt that'
by _puk 5y ago
Process debt is another one I've invariably come across and covers the need for loose requirements (especially early on).
There's a lot of technical debt that's going to accrue before the process debt is sorted if you're trying to scale quickly.
- deleted 5y ago[deleted]
- louwrentius 5y agoIf you build with the explicit goal to learn and explore the process and problem domain, and then have to rework code because of new insights and understanding, we are as close to the original definition of technical debt. But it is my impression that this is the rare exception. In most cases, people are just bullshitting to cover up their ineptitude.