Technical Debt is a Skill Issue

We've heard the move fast, break things argument in the past. There's always going to be sloppy code. There is going to be technical debt. Has something actually dramatically changed recently? And how much? — When someone builds something and it wasn't built great often times they use the excuse, well, we had to move quick, so I made these intentional trade-offs. But then you ask them, is that objectively true or was that subjectively true for like the moment in time that you were in? If you were to now go and rebuild the same thing from scratch, would you actually like make all those same trade-offs or was it just that you at your skill level at a certain time could only focus on so much? So, you made certain trade-offs. And it's almost always that's the case. Like anytime I build something, no matter how successful it was, I look back at all the stuff that we did badly, 5% of that was intentional trade-offs. The other 95% of that was inexperienced with my first time doing something or we were like overwhelmed with other stuff. The next time I went and did that, I got almost all that stuff right up