惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
The Exploit Database - CXSecurity.com
F
Fortinet All Blogs
U
Unit 42
F
Full Disclosure
雷峰网
雷峰网
博客园 - 司徒正美
云风的 BLOG
云风的 BLOG
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
The Cloudflare Blog
Last Week in AI
Last Week in AI
罗磊的独立博客
D
DataBreaches.Net
C
Check Point Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
O
OpenAI News
C
CXSECURITY Database RSS Feed - CXSecurity.com
aimingoo的专栏
aimingoo的专栏
S
Security @ Cisco Blogs
大猫的无限游戏
大猫的无限游戏
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
S
SegmentFault 最新的问题
NISL@THU
NISL@THU
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Hacker News
The Hacker News
Webroot Blog
Webroot Blog
Security Latest
Security Latest
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Google DeepMind News
Google DeepMind News
酷 壳 – CoolShell
酷 壳 – CoolShell
N
News | PayPal Newsroom
P
Proofpoint News Feed
B
Blog RSS Feed
MongoDB | Blog
MongoDB | Blog
C
Cybersecurity and Infrastructure Security Agency CISA
N
News and Events Feed by Topic
Google Online Security Blog
Google Online Security Blog
H
Help Net Security
Spread Privacy
Spread Privacy
T
Threat Research - Cisco Blogs
GbyAI
GbyAI
I
Intezer
Application and Cybersecurity Blog
Application and Cybersecurity Blog
M
MIT News - Artificial intelligence
Vercel News
Vercel News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
IT之家
IT之家
MyScale Blog
MyScale Blog
腾讯CDC

CoRecursive: Coding Stories

The Pre-Training Wall and the Treadmill After It The Aging Programmer From Hacker News to TikTok The Universal Paperclip Clicker Inside Early Google https://corecursive.com/debugging-yourself-with-burke-holland/ Godbolt's Rule Risk Rolls Downhill Coding in the Red-Queen Era When AI Codes, What’s Left for me? Coding Through Chaos The Power of Context: Reimagining Learning briffa_sep98_e.pro https://corecursive.com/hatetris-with-david-and-felipe/ One Million Checkboxes Leaving Stripe CoRecursive Podcast ReiserFS From Everest to Startups From Code to Capital Discovering the power of story-telling in engineering | Adam Gordon Bell (CoRecursive) Navigating Corporate Giants From Burnout to Breakthrough Coding Machines Code, Kickflips and Crunch Time Leaving LinkedIn Beautiful Code Code as a Lifeline From 486 to Vue.js Platform Takes The Pain Sloot Digital Coding System Configuring Identity The Science of Learning to Code A Dark Room - From Code Hobo to Indie Game Developer Quitting (And Then Rejoining) Stack Overflow Story: From Project Management to Data Compression Innovator JSON vs XML Sun's Mobile Blunders Shipping Graphing Calculator The Unfulfilled Engineer DOOMed to Fail: A Horror Story Software World Tour Android's Unlikely Success From Prison To Programming CPAN The History and Mystery Of Eliza Why still 80 columns? LISP in Space April Fools' Is Cancelled (2014) The Story Graph Story: Serenity OS Chat: The Internet Is Made of Duct Tape Story: Cocoa Culture Story: Leaving Debian Story: The Original Remote Developer Chat: Quines, Polygot Code, and Other Fun Computations Story: Full-Time Open Source Story: The Untold Story of SQLite Story: From Competitive Programming to APL Story: Ethereum Rescue Story: Apple 2001 Story: Video Game Programming From Scratch Story: Reinforcement Learning At Facebook with Jason Gauci Chat: 2020 Year End Story: Frontiers of Performance with Daniel Lemire Story: The Birth of Unix with Brian Kernighan Story: To The Assembly Story: Memento Mori Story: We are teaching Functional Programming Wrong Story: Software That Doesn't Suck With Jim Blandy Story: Unproven Tech Case Study with Sean Allen Story: Krystal's Story Story: Learning a new language with Bruce Tate Story: Portal Abstractions with Sam Ritchie Chat: Loving Legacy Code with Jonathan Boccara Tech Talk: The Reason For Types with Jared Forsyth on ReasonML and Javascript Tech Talk: Karl L Hughes on Speaking and Conference Talks Chat: Don and Adam discuss folds Story: David Heinemeier Hansson, Software Contrarian Tech Talk: The Business Of Developer Tools With Lee Edwards Tech Talk: Software in Context with Zach Tellman Tech Talk: Beautiful and Useless Coding with Allison Parrish Tech Talk: Tech Evangelism and Open source With Gabriel Gonzalez Tech Talk: Structure and Interpretation of Computer Programs with Hal Abelson Tech Talk: Open Source Health and Diversity with Heather C Miller Tech Talk: Compiling to Bytecode with Thorsten Ball Tech Talk: Bartosz Milewski on Category Theory Tech Talk: Jimmy Koppel on Advanced Software Design Tech Talk: Typescript with Chris Krycho Modern Systems Programming Tech Talk: Learning to Think with Andy Hunt - Pragmatic Programmers guide to being productive Tech Talk: Data and Scale with Pat Helland - The long view on distributed databases Abstraction and Learning with Runar Bjarnason Burn out and recreational coding with Jamis Buck Tech Talk: Software as a Reflection of Values With Bryan Cantrill Tech Talk: The Little Typer With Daniel Friedman and David Thrane Christiansen Tech Talk: Big Ball Of Mud Tech Talk: God's Programming Language - Philip Wadler on Haskell Tech Talk: Test in Production and being On-Call with Charity Majors Tech Talk: Domain Driven Design And Microservices
Podcast Update
2025-09-02 · via CoRecursive: Coding Stories

No Episode This Month

Hey, it’s Adam. Quick update for September 2025. I do not have a full episode ready today. I’ve been making this podcast for years now, and I always at least get out a monthly episode, but I don’t have one. And instead of silence, I wanted to share just a couple reflections on making this podcast: where it’s at, what’s next, why I keep going, why it’s hard.

Can One Episode a Month Be Enough?

My first reflection is about consistency. Consistency versus reality. For me, it feels like this one episode a month is a minimum, right? Anything less, and it doesn’t really feel like a podcast. There’s so much that I’m not doing right. I— I could be doing more frequent episodes. I probably should be doing video.

I should probably have some sort of clips that I share online. I am not keeping my newsletter up to date. There’s a well-worn growth playbook and I just haven’t been keeping up with it.

I have amazing Patreon supporters who should probably getting more custom and bonus content, but it’s hard for me to keep up sometimes. But I had my bar one episode a month and— and breaking that hurts. Consistency is hard because I’m making each episode from scratch each month. And also, you know, I like to experiment.

I’ve done some recent audio essays. I’ve done some smaller stories. I’ve done some research-based stories. And that variation excites me, keeps me interested and engaged in putting out this content. But it does work against consistency. But don’t worry, I have two episodes coming. One is a story about software injustice, someone harmed by a system, by the code behind it.

It’s great storytelling experience. I think, you know, I still have a lot to do on it. The other one is an interview with Matt Godbold. I talked to him five years ago and he’s back again, and it’s just exciting to hear from Matt.

I’m disappointed that neither of these episodes will be out, but I’m choosing quality over the schedule.

Inconsistency versus reality. Reality has won. But if I’m not able to get an episode out, I’ll try to put out a note like this in the future.

Racing Ira Glass to the Deadline

Which brings me to my second point about my struggles, the creative cycle.

There’s this graphic novel. It called Radio— an illustrated Guide. It’s pretty old and it’s about Ira Glass and how he makes this American life. And it has this panel in it where he is like running with a tape to push into a player to like broadcast live on the radio.

Because that is the experience of making this American life, like, every week they are down to the wire to get something out.

And I feel like this podcast is like that as well. After all these years, it’s still a race every month to the deadline. And this creates kind of a— a sign wave effect, right? There is the high points of finding a guest with a promising story and doing sort of a pre-interview and talking to them. But there can be like a slog of doing research and doing scheduling, and make sure you get things in time so that you’ll have time to edit the episode.

And there’s the peak of getting to interview them and getting excited about their story and getting to connect. And then the trough of editing that takes so much time and how the episode won’t seem that great and how it just takes hours to shape it and clean the audio and make the edits sound hopefully all right.

And then, yeah, setting up the website and shipping the episode and all that— it’s not fun for me. But then the high point is getting the episode out, getting listener feedback, hearing people say that they listened to the episode and— and it affected them. It used to be I would get a lot of attention on Twitter and on Reddit for episodes.

That happens less now. I mean, Twitter is different than it used to be. Most feedback comes with people just sending emails or connecting with me on Slack, but I’m grateful for it all. That is a big deal, even if I sometimes forget to get back to people. Recently, Ron listener told me that he and his son listened to the latest episode while he was driving him back to college for his second, his sophomore year in computer engineering, which is wild.

That’s an important trip— important father and son trip in their in their lives. And I’m excited and shocked, that my voice was riding along with them. That’s humbling. But yeah, those messages mean a lot to me, and that’s one of the high points in this sine wave up and down, feeling positive or negative about the podcast.

And I have been hunting for sustainability wins, like ways to make it lower effort to do the episodes, and that may improve some things. But beyond this, like sine wave, uh, each month of getting the episodes done, there’s also just the sine wave up and down of life. The seasons, right? I am a human. I— I have a job, I have a wife, I have other hobbies.

Sometimes I have the energy to go deep and— and sometimes I don’t. And I think that the podcast will end at some point.

I won’t stop creating. I— I like to create things, but I mean, it seems unlikely the show will last forever. But for now, I’m here. I’m working hard at it. I’m doing the work.

Chasing Depth, Not Downloads

Which brings me to 0.3: depth over scale. When I started doing the podcast. You know, in some ways I hope that nobody listened to it because, you know, I didn’t think it was very good, but in other ways I wanted to be the most important person in software development ever. Right? I wanted to be this huge trendsetter and influencer with great— with a great big audience.

But what holds me now is depth, right? Is talking to somebody and really understanding their story and the specific moments in their life. I think that’s where my strength lies. I think there are bigger tech podcasts. There are bigger YouTubers.

I don’t know if I can compete with the large interviews that Lex Friedman shares, but I think I have my own strengths in the recent John Walker episode. I didn’t know his full story, but it unfolded a little bit in the pre-interview and then a lot while we talked and it was powerful for me. And I think about that all the time and I care about those details, right? I care about, you know, where were you sitting when the bug finally made sense?

You know, what did you do? Did you punch the air and say, like, found it? Yes. Did you wake up your wife in the middle of the night accidentally? I like that depth. I like to understand where people were at, and I think that’s impactful for listeners, hopefully, but I think it can also mean that there’s fewer listeners, but that’s okay. Right? I’m aiming for a deeper connection, even if it means fewer downloads.

There have been guests that have been unhappy with the final result of an episode because it shares too much, but that’s okay because I’m aiming for that deeper connection, even if it means fewer downloads. So that’s kind of my third reflection, which is that I will keep choosing that intimacy and depth even at the cost of reach, even if occasionally it means I don’t get an episode.

A Microphone That Changed a Career

So, yeah, there is a new episode coming, more than one, but it’ll be next month. Right? The podcast has been good to me. I’m on my way to Atlanta right now to give a talk about how AI affects cloud infrastructure and that path started here with me talking into a microphone, and now, you know, I create content for developers for a living, different types than what I do here, but I can do it because of this and because of you, I guess because people listened.

So thank you for the notes. Thank you for the feedback because people listen, because people gave me feedback. I kept doing it. I built up those skills and now I have a pretty interesting job. All thanks to that. If you’re a listener and things impacted you.

Yeah, feel free to share your thoughts online or, or send me an email. It does, uh, mean a lot to me, and I don’t always reply to everybody, which I feel bad about, but your messages keep this going. And especially thank you to the people who are supporting me on Patreon.

But yeah, two episodes are coming and when they land, tell me which one that you like and why. And stay tuned for new episodes. Uh, most of all though, thank you for your patience with my cadence and my constraints and the reality of my life. I’m still here, I’m still making this.

And until next time, thank you so much for listening.

Support CoRecursive

Hello,
I make CoRecursive because I love it when someone shares the details behind some project, some bug, or some incident with me.

No other podcast was telling stories quite like I wanted to hear.

Right now this is all done by just me and I love doing it, but it's also exhausting.

Recommending the show to others and contributing to this patreon are the biggest things you can do to help out.

Whatever you can do to help, I truly appreciate it!

Thanks! Adam Gordon Bell

Support The Podcast