Ah yeah, that would be a worry, except I forgot to mention that most of the code I work on usually gets thrown away after like 6 months. Makes tech debt not have nearly as big of an impact on me.

We do have a longer lasting code base that the little widgets I make run off of. That has a much more strict requirements to ensure tech debt is not introduced specifically so we don't end up in that sort of a position.

That said, and yet we couldn't even keep it out of our own code base. So yeah, I think my original comment is just wrong because I forgot all the ways tech debt actually has effected me in the past and how my industry's project cycle is so short term that i rarely have the opportunity to run into tech debt that I caused in a problematic way...

[–] [email protected] 4 points 1 year ago (1 children)

That make sense. Most industry best practices are there to prevent problems that arises when code is evolving over a long period of time.

[–] [email protected] 4 points 1 year ago

Yeah, that makes total sense.

Most software engineers also have to actively maintain and add features to their finished project, and those aspects change a lot about how the problem can be approached.

I failed to take into account why might I have not been effected by tech debt despite occasionally creating it before commenting. Will have to make sure that filter gets a bit stronger lol