CoRecursive: Coding Stories

Ron Garret left JPL for a 100-person startup he'd just discovered on Usenet. Four a.m. alarms. Burbank to San Jose on Southwest. A rented room in Susan Wojcicki's house. He expected the search engine engineering and instead he got asked to build ad serving. In Java and with JSPs and no syntax highlighting and no delimiter balancing. Launch week was a stampede and then a window on his screen fills with declines. Numbers he can't explain. Some of them look… real. How do you even name what's happening?    This episode is about creating Google AdWords. Building the machine that prints money, while trying not to get crushed in the gears. Episode Page Support The Show Subscribe To The Podcast Join The Newsletter  

Imagine facing a problem you can't name, something that feels bigger than any bug you've ever had to fix. How do you debug your own mind when you don't even know what's wrong? Burke Holland's story starts with a college party and a bad trip that leaves a deeper mark than he expects. Sleep gets harder. Fear creeps in. His life starts shrinking. School falls apart, friends drift away, and he ends up back at home trying to understand what's happening to him. He looks for structure in the Coast Guard. Later he discovers computers and realizes he might have found the thing he's meant to do. But the shadow that followed him out of that party doesn't care about career paths. It shows up during college, during work, during marriage, during parenthood. Sometimes it's quiet, sometimes it knocks him completely flat. This is the story of a developer who looks effortless on stage but spent years fighting something no one else could see, and what changed once he finally understood what he was up against.   What do you do when the hardest problem in your life isn't in your code, but in yourself? Episode Page Support The Show Subscribe To The Podcast Join The Newsletter  

What do you do when your code breaks and the only fix is to dig into the runtime below? Matt Godbolt lives for that. Tile-based renderers, color-coded scanlines, zero-copy NICs—each story is a clue that leads past the abstraction to the real machine. He shares the rule that guides him: master your layer, learn the one below, and know the outline of the layer under that.  Matt Godbolt's journey proves the real breakthroughs are hideen behind the abstrations where you are comfortable and familiar. Episode Page Support The Show Subscribe To The Podcast Join The Newsletter  

What if a software bug drained your savings, ruined your reputation, and nobody believed it wasn't your fault?  Scott Darlington took over a village post office, hoping to give his family a steady life. But the software system kept showing cash shortfalls he couldn't explain. Each time, the Post Office told him the numbers were right and made him pay the difference out of his own pocket.  Eventually it became too much and actions Scott took to protect himself lead to his arrest and public shaming.   How do you build trust in systems when the people behind them refuse to admit they're broken?

A quick update from Adam about the podcast's current state, consistency challenges, and what's coming next.  Episode Page Support The Show Subscribe To The Podcast Join The Newsletter