If I hear anyone utter the words "technical debt" one more time, I swear to God, I will fucking kill them :-/

It's your fault your design smells like piss in the first place. It's your responsibility to fucking fix it. You can't just sit on your arse all day, coming up with new, "innovative" ideas that will build up more technical debt :-/ it's making the life of everyone around you, a big, irreparable mess.

Incoherent monolithic legacy inheritance...

Would this be a more suitable term?

@C0D4 okay, maybe I won't kill you. But I'll chop off a finger or two.

@C0D4 I've decided I'll chop off three.

One for 'monolithic'
One for 'incoherent'
One for 'legacy'

Woah, all that abuse and then, the word 'arse'.

Trying to be British, are we?

@nik0333 'arse' maybe British but equally as pejorative as 'ass' :-P

Also, tit for tat-ing, are we?

@byte-me Indeed, we are!

Btw, why don't you rather byte @C0D4 's fingers off?

@nik0333 be nice, not all inheritances are good to have 😅

@C0D4 I am, it was just a take on her username. Read the word "byte"?

Correct me if I am wrong, since it's a term I rarely get the chance to use, but incurring technical debt is often a conscious decision (or should be) much like taking a credit at a bank.
It also happens because of compensating for unreasonable deadlines or the unjustified anxiety of non-tech decision makers that makes them to just see something working and ship it.

What I mean is, sometimes the term isn't the developer's fault. A " serial reckless inovator" probably falls outside that scope though 😅

I totally agree you with, especially the unjustified anxiety if the higher ups and the unreasonable deadline part!

A previous employee may have accumulated all the tech debt and it may not be the current developer's fault, but it matters what they prioritize, right.