[literallyaduck]

Maintainable code is a fools errand people just need the lingo for the interview, people don't stay at the same job long enough to really worry about it long term. People ship the one to throw away then the next devs rewrite everything their foredevs wrote. Languages, databases and standards are moving targets and today's best practice is tomorrow's antipattern.

If you want to ensure that you hire devs who have longevity in your product only hire devs who have worked in the same place long enough to pay for their coding choices and ask them for specific times they had technical debt and what steps they took to remedy the problem. You will find out more by letting them talk.

[moneywoes]

Let’s say I’m in an interview situation, how do I implement this lingo? Additionally I wholeheartedly agree with you based on what I’ve seen at work