|
|
|
|
|
|
by carl_sandland
1257 days ago
|
|
|
There's no such thing as 'technical debt', just call it crap code (or a 'hack') and face the impacts of having to live with it. Its been my experience that these things get logged to Jira as 'medium' or 'low' and then of course never get looked at again, and if they ever get opened up its likely the code has moved on. This leads to the following idea; 1. code the MVP the customer accepts (customer is happy)
2. go ahead and create all the debt tickets (makes you feel professional)
3. every xmas just delete all non-high tickets older than 12 months. If the code is shit enough, it will die a natural death (most of today's wiring type code has very short TTL anyways) Similar to "if a tree falls in the forest...", "If a customer doesn't notice...". We do so many 'invisible', 'hard' things in our line of work, it's almost an impossibly thankless road to build quality into our systems. |
|
|