How to Avoid Technical Debt in Django

I think people forget about the human cost of all of this. If your site's going down half the time you're deploying and your team is constantly like waiting for the next fire to happen, you're going to get burnout. People are going to leave if they can't do that for a sustained amount of time. I worked with this company Quizlet that's now grown. And so why do companies get themselves in this holes of technical debt? You know, it's partly because they didn't know any better. But it's also partly because like they've got their own fires to deal with.