Sam: The man so many of us knew as Bob Cringely... has passed away.
Kai: And just like that, a piece of tech history is gone. I'm Kai.
Sam: And I'm Sam. This is Trending Repos for Sunday, October 4th, 2026.
Kai: We're starting on that somber note, but we still have three big stories from the developer world for you.
Kai: Coming up, we'll remember the life and impact of tech journalist Bob Cringely.
Sam: Then, we're asking a huge question for anyone on the cloud: should your account just… die when you hit your budget?
Kai: And we'll get into a developer's ranked list of reasons they didn't become an EMT. It is a tough read.
Sam: So let's start on Hacker News, with the passing of Mark Stevens—better known to all of us by his pen name, Bob Cringely.
Kai: Man... if you were online in the 90s or 2000s, Cringely was the voice. His column, 'I, Cringely,' the PBS doc 'Triumph of the Nerds'... he explained the PC revolution to millions.
Sam: The Hacker News post mentions he was an early Apple employee. This wasn't just a journalist, this was someone in the room for some of the biggest moments in tech.
Kai: Exactly. He had that insider perspective but made it accessible. He made nerds feel like rock stars by treating their stories like they mattered.
Sam: And that whole pseudonym thing is fascinating, right? In this age of personal branding, 'Bob Cringely' was a shared identity, even passed between writers. It was about the column, not the person.
Kai: It gave him freedom, right? He could be irreverent, he could speculate, he could call out Steve Jobs in a way 'Mark Stevens, Apple employee number twelve' maybe couldn't.
Sam: It's a good lesson for creators today. Sometimes the work speaks louder when your face isn't attached. Let the project be the star.
Kai: What really stands out to me was his passion. He just loved this stuff. He saw the drama, the humanity in building software. We try to bring a little of that here every day.
Sam: He'll be missed. A true original.
Kai: Okay, let's move on to something Cringely probably wrote about a thousand times: surprise bills. Simon Willison posted an argument that we need default hard budget caps on... well, pretty much everything.
Sam: Ah yes, the classic 'I woke up to a ten thousand dollar cloud bill' horror story.
Kai: Willison's point is that for indie devs and hobbyists, the default should be safety. You set a ten-dollar budget, and when you hit it, the service just stops. End of story. No surprises.
Sam: Okay, but 'stops' is a gentle word for 'your entire application goes offline'. Right when you're getting a huge traffic spike from Hacker News, your database just... vanishes. Is that really what you want?
Kai: For a hobby project? Yes! A thousand times yes! I would rather have my side project go down for a day than get a bill that bankrupts me.
Sam: But the cloud providers have zero incentive to do this. Their model is 'pay for what you use,' and they make a killing on overages. Billing alerts are their so-called compromise.
Kai: But alerts are useless! You get an email saying 'You might spend a thousand dollars' when you've already spent eight hundred. It’s an alarm bell for a fire that's already taken hold. We need a circuit breaker.
Sam: So the user experience is: 'Welcome to my cool new app! Sorry, it's offline because it got too popular.' That's a bad look.
Kai: It's better than 'Welcome to my cool new app! To keep it online, please help me pay this fifty thousand dollar bill I accidentally racked up.' We see those GoFundMes all the time!
Sam: I see the appeal, I do. But this feels like asking for a car that automatically shuts off the engine if you exceed the speed limit. It's a safety feature that could cause a bigger accident.
Kai: So the takeaway for developers is, you can't wait for AWS or Google to fix this. You have to build your own kill switch. Use services like Vercel or Fly.io with clearer pricing, or write a script that shuts things down via API when you hit a limit.
Sam: Be your own hard budget cap. I guess that's the only option for now. Just be very, very careful what that shutdown script does.
Kai: Alright, our last story today is a blog post from Ben Stolovitz called 'Reasons I didn't become an EMT, ranked.' It's not something you'd expect on a tech feed, but it's really hitting a nerve.
Sam: 'Hitting a nerve' is one way to put it. It's a brutal, honest look at a high-stress, low-pay job that our society completely depends on.
Kai: He actually ranks the reasons—and my developer brain loves the structure—but the reasons themselves are just brutal. Number three is 'The pay is insulting.' He figured out it would be a fifty percent pay cut from his internship.
Sam: And his number one reason? 'I wouldn't be a good EMT.' The self-awareness there is incredible. He talks about the psychological toll, the things you'd see... and just admits he's not built for it.
Kai: It's such a stark contrast to the 'move fast and break things' ethos in tech. This is a world where breaking things has immediate, irreversible consequences.
Sam: It just goes to show, you can't 'disrupt' or optimize everything with an app. Some jobs are just fundamentally hard, and we systematically undervalue the people who do them.
Kai: Right. So if you're a dev reading this, it's a huge reality check. We complain about being on-call, but this is literally life-and-death on-call.
Sam: It's perspective. Your production database going down is a crisis, but it's not the same as someone having a heart attack. It's good to remember that, especially when we talk about burnout in our own field.
Kai: It definitely makes you grateful for our salaries and tools. But maybe it's also a call to think about how we can support these other fields—not by trying to replace them, but by building things that actually help.
Sam: A little less 'Uber for ambulances' and a little more 'better scheduling software for EMTs.'
Kai: Exactly.
Kai: So today we said a sad farewell to tech journalism legend, Bob Cringely.
Sam: Dug into the fiery debate on hard budget caps for cloud services.
Kai: And got a dose of perspective on the tough realities of being an EMT.
Sam: And before we go... in honor of Bob Cringely and the era he defined, I was looking at some retro-computing projects on GitHub.
Kai: Oh, nice. What did you find? A cool new Mac OS 9 emulator?
Sam: I stumbled across 86-Box. It’s a low-level emulator for old x86 hardware. Not new, but the team is so dedicated. They're emulating specific sound cards, graphics cards... it's a living museum of the machines Cringely wrote about. A really cool way to touch that history.
Kai: That's a perfect tribute. And that's our show for today. Thanks for tuning in to Trending Repos.
Sam: We'll be back tomorrow. In the meantime, maybe go set some billing alerts. Or just be ready to pull the plug yourself.
This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.