Dear past Jenna,
I know you're used to dealing with large, complex, legacy codebases riddled with technical debt. And for the longest time, that was kind of your thing. You'd unwind them, figure out how to insert a feature here without breaking functionality there, or discover that customers had come to depend on something that was technically a bug.
I recently saw this post on X (it's no longer a tweet on Twitter, but that's a story for another day):
Technical debt used to be something you just had to live with in a sufficiently large codebase. No longer.
The replies and reposts were all over the place, but a number of them went like this:
