btables
Re:13 Months Sober (2025)
on Monday September 28, 2026 @01:22PM (#49881355)
Congrats on 12 years and sharing that story. More people should hear about these moments.
Re:13 Months Sober (2025)
on Monday September 28, 2026 @01:21PM (#49881329)
Alcohol was a net-positive in so many ways for me. I talk more about that aspect in the 6 month post here: https://www.bobbytables.io/p/six-months-sober
The Architecture Behind Our SSE Streams
Using Modal for GLM Flash on Cadenya's Agent Runtime
Re:OpenAI Agents API
on Thursday September 10, 2026 @07:04PM (#49651325)
Just letting you know, this comment inspired me to finally just say "screw it" and launch what I've been building for the past year. https://www.cadenya.com
Show HN: Cadenya – An Agent Runtime
My name is Robert, and I'm the founder of Cadenya, an agent runtime.Cadenya is not like other managed solutions. Instead, it uses your API or MCP servers as the tools in your agentic loop, which also is managed.Cadenya is also agnostic to the model provider. Wire up OpenRouter, or any OpenAI compatible endpoint, and it will use it for inference.It also supports agent variations - where Cadenya...
Re:One Protobuf Schema for REST, Postgres, SDKs, and Docs
on Sunday September 06, 2026 @09:36AM (#49586422)
I wrote this up because I haven't found many end-to-end posts that explain how to go from Protobuf to an implemented API, to SDKs, to API docs. There's a lot of wires to plug in, but once you're there. It's magical. So here's my writeup on it for Cadenya.
One Protobuf Schema for REST, Postgres, SDKs, and Docs
Re:Ask HN: Who is using MCP in production?
on Thursday September 03, 2026 @10:30PM (#49559823)
Building an agent runtime at cadenya.com and MCP servers have been the hardest part to create adapters for. For a two year old spec, there's far too many permutations.
Re:The Agentic Loop: Three loops in a trench coat
on Tuesday July 14, 2026 @02:38PM (#48911254)
Totally. Earth's rotation is a loop too. We should count that.
Re:The Agentic Loop: Three loops in a trench coat
on Tuesday July 14, 2026 @12:23PM (#48909227)
I think of them from the outside in, so that's why I illustrated it that way.
The Agentic Loop: Three loops in a trench coat
LLMs don't want pixels, they want tools
Sidekiq to Temporal: a zero-downtime migration strategy
Natural Opinions
Microsoft and My Tinfoil Journey
Hot Take: Don't provide incident resolution estimates
FireHydrant Has Acquired Blameless
PagerDuty Migration Tool for FireHydrant
Show HN: FireHydrant on-call and alerting alternative to PagerDuty
FireHydrant's on-call and alerting tool is now GA
SVB and the internal play-by-play of FireHydrant's response
Your codebase Is a Jenga Tower
Incident Travel Time
Re:Integrations on Rails: How we build and deploy integrations at Fire...
on Monday November 28, 2022 @02:16PM (#33778169)
It’s been a minute since I wrote a technical blog post about FireHydrant, but I think I’m making up for it with this doozie. Check out how we structure our integration architecture in a way that’s allowed us to release a new integration every month for the past three years.
Integrations on Rails: How we build and deploy integrations at FireHydrant
FireHydrant releases service dependency graphs
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
on Tuesday June 07, 2022 @11:03AM (#31655413)
Thanks, emailed you as well. Sorry you ran into this!
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
on Tuesday June 07, 2022 @11:02AM (#31655389)
firehydrant.com has a free tier that allows people to open incidents from Slack. It also includes the service catalog, runbooks, and status pages.