Dead Code

Jared talks with Joan Westenberg about her essay “The Hacker News Tar Pit” and the misconception that AI-powered vibe coding can easily replace established products. Joan argues that while AI can generate software, it cannot recreate the communities, culture, trust, moderation systems, shared history, and network effects that make platforms like Hacker News valuable. The conversation explores how online communities form organically, why moderation and human labor matter more than code alone, and how AI-generated spam is changing the nature of internet communities. They also discuss open source software, the flood of vibe-coded projects, and the psychological effects of constantly comparing your work to what others are building online. Joan ultimately argues that developers should build things because they genuinely want them to exist, not because they expect to disrupt incumbents, while Jared closes by reflecting on an AI-generated compiler he built that worked technically but failed to inspire the long-term interest needed to turn it into a real project.

Links:

The Hacker News Tar Pit (Joan Westenberg)
Hacker News
Lobsters
Schelling Point
RubyKaigi
Yukihiro “Matz” Matsumoto
chorus.fm
Something Awful
Digg
Cal.com
Love2D
Lua
Hindley–Milner Type System
Studio Self
Joan Westenberg

Dead Code Podcast Links:

Mastodon
X

Jared’s Links:

Mastodon
X
twitch.tv/jardonamron
Jared’s Newsletter & Website

Episode Transcript
Hosted on Acast. See acast.com/privacy for more information.

In this episode of Dead Code, Kasper Timm Hansen shares how his post–Rails Core work focuses on small, high-impact Ruby gems built around clear “concepts” rather than loose abstractions, helping developers model domains more effectively and avoid bloated ActiveRecord models. He discusses tools like Associated Objects and ActiveJob::Performs, which simplify structuring data and background jobs while reducing boilerplate, and Oaken, a testing approach that blends fixtures and factories into fast, scenario-driven data scripts. Across all his work, Kasper emphasizes keeping code minimal, readable, and easy to maintain, using constraints like line count to guide design. He also touches on his current project, Peak and gem.coop, where he’s exploring improvements to the Ruby ecosystem such as namespaced gems, dependency cooldowns for security, and better ways to manage and trust dependencies, all driven by an experimental mindset aimed at making development more intuitive and efficient.

Links:
I quit Rails core 4 years ago, here’s what I’ve been up to
Kasper Timm Hansen
Ruby on Rails
Associated Objects gem
ActiveJob::Performs gem
Oaken
Active Record
Active Job
Factory Bot
Rails fixtures
Delayed Job
Singleton classes in Ruby
gem.coop
Peak (gem.coop project)
RubyGems
Bundler compact index
Supply chain security (overview)

Dead Code Podcast Links:

Mastodon
X

Jared’s Links:

Mastodon
X
twitch.tv/jardonamron
Jared’s Newsletter & Website

Episode Transcript
Hosted on Acast. See acast.com/privacy for more information.

In this episode, Jared talks with security researcher Lyra Rebane about pushing CSS far beyond its reputation as a simple styling language, exploring how modern features like nesting, advanced selectors, and state-based logic enable complex interactivity without relying on JavaScript. Inspired by experiments on Cohost, Lyra created projects like a fully CSS-based clicker game and even an 8086 CPU emulator that can run compiled C code using CSS variables, animations, and clever workarounds. The conversation highlights how developers often overuse JavaScript for tasks CSS can handle more efficiently, while also challenging the industry’s tendency to dismiss CSS work as less valuable, arguing instead that treating CSS as a true programming language opens up both technical possibilities and greater respect for front-end expertise.

Links:

Cohost platform
CSS nesting
:has() selector
CSS variables (custom properties)
CSS animations
CSS container queries
Cookie Clicker (incremental game example)
x86 architecture overview
8086 CPU
C programming language
Content Security Policy (CSP)
Cross-site scripting (XSS)
SVG filters

Dead Code Podcast Links:

Mastodon
X

Jared’s Links:

Mastodon
X
twitch.tv/jardonamron
Jared’s Newsletter & Website

Episode Transcript

Hosted on Acast. See acast.com/privacy for more information.

In this episode of Dead Code, Jared talks with developer Dave Copeland about his article “The Death of the Software Craftsman,” which reflects on how AI coding tools are reshaping the role of programmers. Copeland describes a personal reckoning with whether traditional programming skills still matter in a world where AI can generate large amounts of code. He outlines three possible responses for developers: refusing to use AI, going all in on AI-assisted development, or “embracing tradition” by positioning oneself as a craftsperson who writes higher-quality code by hand in areas where reliability and accountability matter. The conversation explores the tension between programmers who enjoy the craft of coding and businesses that primarily care about outcomes, suggesting that as AI becomes more common, developers may need to focus less on code elegance and more on measurable results like reliability, safety, and system performance while learning how to work effectively alongside AI tools.

Links:

The Death of the Software Craftsman
Dave Copeland
Brut Ruby Web Framework
Ruby Programming Language
Ruby on Rails
Software Craftsmanship Movement
SOLID Principles
Dependency Injection
Cross-Site Request Forgery (CSRF)
Agile Software Development
Observability in Software Systems
Large Language Models (LLMs)
Accidental Tech Podcast

Dead Code Podcast Links:

Mastodon
X

Jared’s Links:

Mastodon
X
twitch.tv/jardonamron
Jared’s Newsletter & Website

Episode Transcript
Hosted on Acast. See acast.com/privacy for more information.

Sean Goedecke contrasts generic design advice (principles and patterns not grounded in a specific codebase) with concrete design (decisions shaped by the real code, constraints, and existing “prior art”), arguing you can’t meaningfully design software you don’t work on because you lack the context to make implementable calls. Generic advice has its place (greenfield work, company-wide guardrails), but in large, messy systems consistency matters more than isolated “good design,” because teams survive by reusing known patterns and keeping the codebase coherent. He’s skeptical of architect handoffs where designs ignore practical timelines and incentives reward complexity, and he notes AI coding tools behave like smart outsiders—useful, but prone to reinventing what already exists unless humans with deep context guide them.

Links:

Sean Goedecke’s article: “You can’t design software you don’t work on”
SOLID principles (overview)
Single-responsibility principle (SRP)
GitHub Copilot (product page)
GitHub Copilot code review (docs)
Claude Code (Anthropic product page)
GitHub adding Claude + Codex agents (The Verge)

Dead Code Podcast Links:

Mastodon
X

Jared’s Links:

Mastodon
X
twitch.tv/jardonamron
Jared’s Newsletter & Website

Episode Transcript
Hosted on Acast. See acast.com/privacy for more information.