Dead Code seeks to extract the good ideas from the chaos of modern software development. Hosted by @jardonamron.

Joined August 2023
Dead Code@DeadCodePodOct 21
Scrolling memes about a topic can feel like learning. Alistair Norman says vibe coding gives you the same quick hits of progress. The deep understanding comes from school and academic research, even when that feels like a grind.
1
2
50
Dead Code@DeadCodePodOct 16
DHH's Rails World keynote measured AI-assisted coding in lines of code. Alistair Norman thinks he chose that number because he didn't have a better one. Work that actually helped people would have come with a metric to show for it.
1
1
25
Dead Code@DeadCodePodOct 16
Agents can spin up an app fast, and that speed is fun at first. Sofia Besenski says design principles still apply once the shine wears off. She compares it to Martin Fowler's idea that skipping design works only until a project plateaus.
1
2
24
Dead Code@DeadCodePodOct 14
DHH compared lines of code at Rails World as if more meant better. Sofia Besenski calls that tokenmaxxing. An agent running in a loop could write a million lines of Rust in a month, and it wouldn't make her a better developer.
1
2
59
Dead Code@DeadCodePodOct 13
HEY is trading one Rails app for six native apps and a Rust backend. Sofia Besenski sees six new sets of failure points. She also points to research on cognitive debt, where engineers stop understanding the systems they're building.
1
2
36
Dead Code@DeadCodePodOct 7
"I can probably count on one hand the number of times I've been glad that I didn't delete a piece of code." Kerri Miller used to think an uncalled method did no damage and more tests were always better. About 30 years in, she's stopped keeping code around in case she needs it.
1
19
Dead Code@DeadCodePodOct 2
One harmless-looking test was creating more than 80 records every time it ran. Kerri Miller says it didn't test anything interesting, so she deleted it. Years of using code analysis tools have made her think about the cost of every decision in the code she writes.
1
16
Dead Code@DeadCodePodOct 2
Code that sits between two teams tends to rot because neither feels responsible for it. Kerri Miller points to Rails partials, which are written in Ruby but get more attention from front-end engineers. That's where she wants to take Keela next. She'll be happy with 80% accuracy.
1
1
25
Dead Code@DeadCodePodSep 30
Kerri Miller built Keela to stay out of engineers' way, and she kept receipts to show it was worth it. Removing dead code at GitLab now saves about $150,000 a year in CI costs. It also cut the app's overall compute complexity score by around 2.5%.
1
25
Dead Code@DeadCodePodSep 29
Most big codebases have a layer where someone changed everything at once. Kerri Miller compares it to the K-T boundary in the fossil record. Those sweeping commits touch hundreds of files and break git blame. Keela takes the slower route and blocks new dead code as it comes in.
2
31