Catch the full show here: shows.acast.com/dead-code/e...
06.03.2026 16:15
👍 0
🔁 0
💬 0
📌 0
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.
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.
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.
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.
If you cannot explain what you shipped, you do not really own it. Daniel Fichtinger has practical advice for fixing that.
If you care about healthy beginner spaces, listen to Daniel Fichtinger on why slop spreads so fast.
Ever click a “new project” link and immediately feel skeptical? Daniel Fichtinger breaks down what that instinct is catching, and why it matters.
Daniel Fichtinger on the real slopware tell: it is not “used AI,” it is the gap between promises and reality.
Need a quick gut-check for whether an open source project is worth your time? Daniel Fichtinger shares the trust signals that actually matter.
Tune in if you’re trying to make Tailwind scale without hating your codebase: shows.acast.com/dead-code/e...
Hit play if specificity wars have ever made you question your life choices: shows.acast.com/dead-code/e...
Stephen Margheim outlines a middle path between Tailwind class soup and component sprawl.
He shows how to compose higher-level styling in Tailwind while keeping tree shaking, autocomplete, and flexibility, so teams ship faster without a pile of one-off classes.
Stephen Margheim explains a modern CSS trick that makes defaults behave like defaults.
He digs into the specifics of zero-style, which keeps overrides predictable and composable, especially in real design systems.
Listen for the analogy that makes affordances instantly click: shows.acast.com/dead-code/e...
Stephen Margheim uses a door handle metaphor to explain design systems.
Good UI signals how it’s meant to be used without labels or hacks. Margheim connects that idea to affordances and how naming that middle layer improves consistency.
Press play if you’ve ever wanted just the styles and got a whole framework instead: shows.acast.com/dead-code/e...
Stephen Margheim makes a brutal point. Components are a bad delivery mechanism for “just styles.”
If you’ve ever tried to borrow a component kit’s look and found it welded to structure and behavior, Margheim explains why that pain is baked in and what to do instead.
Hit play for the exact approach you can steal without dragging in JS: shows.acast.com/dead-code/e...
Stephen Margheim built a star rating UI with no JavaScript that still submits like a real form input.
Most star widgets are pretty theater until the backend needs an actual value. He breaks down half-star ratings using plain HTML & modern CSS, without the hidden input duct tape.
If you’ve ever felt trapped by your own stack, press play.
Listen: shows.acast.com/dead-code/e...
Kubernetes, cloud services, functions, frameworks: the benefits are obvious…until you’ve lived with them for a year.
Samir Talwar breaks down the hidden costs teams don’t account for (and why so many companies are building like they have billions of users).
