Address 'technical debt' as a technical support engineer [closed]

I was hired urgently for a several months long project as a technical support engineer, but I resigned after a week. This caused the outsoursing company to be obligated to pay a penalty for their client. The reason I resigned was the too large amount of technical debt we had with our tools / the underestimated hardware capacities, which I phrased in a letter before I decided to resign, but got no response. Now they asked me to elaborate more on what I mean under their 'technical debt'. Firt of all, if I understand well, this term is used between developers and not end users. What would be the best term for an end user? Also, I cannot really say much, when the issues started to accumulate, I was thinking about to list them, but then I let it go and just made the decision based on the week's impression. Finally, I know that in the software industry (and about anywhere) the usability is not over any other goals resulting in shiny but quite buggy/bloated with design flaws products. So some kind of tolerance is necessary in this field, it was just too much for me. Any idea is appreciated on how to handle this. EDIT: Clarification: nor the outsourcing company nor the client developed the tools, they bought them.

Jan 16, 2025 - 02:40
Address 'technical debt' as a technical support engineer [closed]

I was hired urgently for a several months long project as a technical support engineer, but I resigned after a week. This caused the outsoursing company to be obligated to pay a penalty for their client.

The reason I resigned was the too large amount of technical debt we had with our tools / the underestimated hardware capacities, which I phrased in a letter before I decided to resign, but got no response.

Now they asked me to elaborate more on what I mean under their 'technical debt'.

Firt of all, if I understand well, this term is used between developers and not end users. What would be the best term for an end user?

Also, I cannot really say much, when the issues started to accumulate, I was thinking about to list them, but then I let it go and just made the decision based on the week's impression.

Finally, I know that in the software industry (and about anywhere) the usability is not over any other goals resulting in shiny but quite buggy/bloated with design flaws products. So some kind of tolerance is necessary in this field, it was just too much for me.

Any idea is appreciated on how to handle this.

EDIT: Clarification: nor the outsourcing company nor the client developed the tools, they bought them.