Have you ever opened a file to make a quick change, only to find dozens of lines of commented-out code making it nearly impossible to understand what's actually running?
In the latest episode of the No Compromises podcast, we discuss why keeping dead code around is slowing your whole team down.
We make the case that commented-out or unused code creates real confusion when searching a codebase, whether you are a new developer, a consultant, or even an AI agent trying to understand what is actually in use.
We also cover why Git is all the safety net you need, how Git bisect can recover deleted code you thought you might need someday, and why the fear of deleting code is almost always unfounded.
- (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
Join the conversation and share how your team handles dead code in our
No Compromises community
Episode 153
