Dead Code

Full episode: shows.acast.com/dead-code/epis…

You can build three “well-designed” subsystems and still end up with a disaster. Sean Goedecke talks about how smart engineers create Frankenstein codebases when they optimize locally instead of matching existing patterns. Great reminder that coherence is a feature.

Listen to the full episode: shows.acast.com/dead-code/epis…

Most “design advice” is just vibes unless you’ve lived in the codebase. Sean Goedecke breaks down the gap between generic principles and real design decisions shaped by actual constraints. If “just refactor it” came from someone who’s never opened the repo, this one’s for you.

Listen to the full episode: shows.acast.com/dead-code/epis…

The best design conversations sound like: “pull up the file.” Sean Goedecke describes a GitHub offsite where the discussion was painfully code-specific, and that’s exactly why it worked. No philosophy, no framework worship, just the actual system and what it can handle.

Dive into the full episode at shows.acast.com/dead-code/epis…

Russ Olsen drops the thesis every doc writer and teacher needs tattooed on their brain: the subject of your work is the reader. The tool does not change. The human does. If you write docs, teach, or lead devs, this clip hits.

Catch the full show here: shows.acast.com/dead-code/epis…

Russ Olsen gives a sharp, practical critique of gradual typing in Ruby. Not anti-types, not anti-safety, just brutally honest about the tradeoffs when the type system is optional, and the annotations start getting more complex than the code.

Listen to the full show at shows.acast.com/dead-code/epis…

Russ Olsen has the most accurate take on the emotional experience of learning a new language: if it looks foreign enough, your brain labels it as wrong. Then you live with it, and suddenly it is normal. This clip is a perfect reminder to stay curious instead of defensive.

Go listen to the full episode at shows.acast.com/dead-code/epis…

Russ Olsen explains why people glaze over when you teach features in the abstract and why seeing one real use case in real code flips the switch. If you have ever learned something only after watching it used “in the wild,” this clip is for you.

Listen to the full episode at shows.acast.com/dead-code/epis…

Ruby can be fast, elegant, and still crystal clear. Russ Olsen nails why “works” is not the same as “readable,” and why the best code pulls double duty as both a machine and a message to the next human.

Get the full conversation: shows.acast.com/dead-code/epis…

If you cannot explain what you shipped, you do not really own it. Daniel Fichtinger has practical advice for fixing that.

Tap to listen: shows.acast.com/dead-code/epis…

If you care about healthy beginner spaces, listen to Daniel Fichtinger on why slop spreads so fast.