That may not be the choice Twitter has made in this instance, but it's a viable choice nonetheless. Defaulting to tech debt = evil wrong imo.
Essentially it's a 'free' internal debt, regardless of how often architects and developers complain of its cost.
Thus in a contest between doing something right, but expensively, versus good-enough-for-now but technically-constrained the latter will usually win.
The cost is reduced development velocity, and perhaps reduced systems stability.
Financial debt has clear cost; technical debt doesn't. So it seems 'free' to the non-technical.
"I'm the Technical Debt Fairy. If you leave technical debt under your pillowcase at night I hire away your best developers"
And I encourage everybody to make that their standard. Now I never cut a corner without that. I never even offer. My default is a zero-additional-tech-debt approach, because that's the only thing I think is responsible or sustainable. If there's a legitimate business need for taking on a bit of tech debt, I will propose the deal of splitting the work into, say, "experiment" and "cleanup", but cleanup ends up in the workstream with a date attached. If the stakeholder accepts the deal but fails to honor it, I revoke their tech-debt credit card.
Also, if we're talking of debt, Twitter ought to be more concerned about its VC debt (investment).
"There is no such a thing as a temporary change or workaround: In most cases, workarounds are tech debt."