logo

Your codebase is not a museum for old code

Commented-out code and dead lines are quietly slowing your team down

Joel Clermont
Joel Clermont
2026-06-01

That block of commented-out code you left behind just in case is costing your whole team something.

In the latest episode of the No Compromises podcast, Aaron and I talk about why dead code and commented-out lines linger in so many projects, and why they do more harm than good. They muddy your search results, they slow down anyone trying to understand the code, and these days they even confuse the AI agents reading your codebase.

We also dig into why Git already gives you all the safety net you need to delete with confidence, including how Git bisect can help you recover something you thought was gone for good.

  • 00:00 Why commented-out code slows everyone down
  • 02:03 How dead code creates false search results
  • 05:10 Dead code costs you more with AI agents too
  • 05:55 How Git bisect helps you recover deleted code
  • 10:08 When commenting out code is actually fine
  • 11:45 Silly bit

Listen Now (14 min)

And after listening, don't forget to subscribe to the podcast, so you don't miss future episodes.

Here to help,

Joel

P.S. If your codebase has accumulated years of dead code nobody wants to touch, we can take a fresh look. Get a Laravel code review.

Toss a coin in the jar if you found this helpful.
Want a tip like this in your inbox every weekday? Sign up below 👇🏼
email
No spam. Only real-world advice.