[giancarlostoro]

I get it. This is roughly me, I don't always have the best answers, but I know most things can always be done better. I've coined a few different terms over the years such as "marketing driven development" when I wind up working in places where the marketing team is driving the devs off a cliff, and pushing new features at the expense of ever having time to deal with technical debt. The industry really needs "Tech Debt Thursdays" or something.

There's always way more work to do and those key enhancements or research stories that could improve everything get deprioritized.

[leetrout]

I didn't RTFA - just responding to you:

> Tech Debt Thursdays

Yes, "Fix it Fridays" is another alliteration.

Have you ever heard the phrase "man your battle stations"? Turns out in the US Navy there is also "cleaning stations" and there is a call for all hands to cleaning stations on the regular. I have proposed something similar on a few teams I've been on. Daily won't work and quarterly is too long. The problem is the sprawl that comes from cleaning up things that have unintended side effects. But yes, paying the interest on the tech debt needs to be normalized across our industry.

https://www.navy.mil/Press-Office/News-Stories/display-news/...

https://www.youtube.com/watch?v=fyJH8VbFE6g

[shadowgovt]

As of late, I've been thinking about how "debt" may not be the right metaphor.

Fiscal debt is a one-dimensional number that becomes higher or lower from some offset, but it can't change direction. There's no "complex numbers debt."

But software engineering is only one-dimensional if your problem domain is so constrained that the only roadblock to execution is time-at-keyboard, and that's rarely the case in most software (especially startups and hacking). I've too often seen that debt just "evaporates" when the company pivots or the entire system is replaced by another system or rendered completely irrelevant to continue accepting the notion that debt works as a metaphor. Even in the small, too often I've seen things flagged as, for example: "debt - we should consolidate these two pipelines on top of a smaller set of helpers" only to see the use of the pipelines diverge over time such that it turned out to be a great first step to keep them separate and duplicated.

Sometimes things to be improved / cleaned up are obvious, but cleanup assumes taking disorder and making order out of it, and that requires us to know what order even looks like.

[giancarlostoro]

There's also in some places 'Friday Afternoon Projects' (also known as FAP iykyk) where you're allowed to work on anything, I'd honestly prefer companies allow me to work on whatever I want once a week so I can put energy into tech debt items, and tools that might make everybody's lives easier.