3 ms·
> And so JIRA ticketing subtly but powerfully tends to push developers to work on one ticket at a time, instead, which is often both less efficient and more pro
by minimaxir 10y ago
> And so JIRA ticketing subtly but powerfully tends to push developers to work on one ticket at a time, instead, which is often both less efficient and more prone to drastic late-in-the-game failure.
Technical debt is measured in net present value.
As a QA engineer myself, it is more valuable to explicitly account for when and why a given software change is made then it is to rush things out, because when a later change inevitably breaks an older one, the engineer can immediately know when and why it happened, and what to fix.
Relying solely on design documents means that if something goes wrong in a sufficiently complex system, it can take a very long time to isolate and fix the issue. (no, TDD does not alleviate this)