Workplace Jiujitsu #14: When No One Asks You To Improve The Code

As a mid-level engineer, you start noticing the gaps: the shortcuts, the "temporary" fixes that became permanent, and the growing technical debt that's quietly slowing everything down. But here's the challenge: projects move fast, and leadership isn't always asking you to fix these issues.

So when do you tackle improvements vs. just keep shipping?

The War vs. Peace Framework

During "war time" (tight deadlines, critical features, crisis mode): Technical debt takes a backseat. Your job is to deliver, even if it means adding to the pile. During "peace time" (stable sprint cycles, breathing room): Reducing technical debt might be the biggest impact you can have. Once you clean up that messy module or refactor that brittle integration, the entire team moves faster.

The Master Craftsman Approach Get so good at your craft that you naturally create less technical debt without sacrificing speed. This means:

Teaching by example through clean, well-documented code
Giving constructive feedback in code reviews
Tackling low-hanging fruit during regular feature work
Communicating the "why" behind technical choices to help teammates avoid similar debt

The key isn't perfection. It's being strategic about when and how you improve things.

How does your team handle technical debt? What's worked (or hasn't) in your experience?