btables

Congrats on 12 years and sharing that story. More people should hear about these moments.

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

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

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.

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.

Totally. Earth's rotation is a loop too. We should count that.

I think of them from the outside in, so that's why I illustrated it that way.

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.

Thanks, emailed you as well. Sorry you ran into this!

firehydrant.com has a free tier that allows people to open incidents from Slack. It also includes the service catalog, runbooks, and status pages.

Yikes! Never like seeing that. Can you email me directly and I will get this sorted? robert@firehydrant.com

I'd checkout FireHydrant, but I'm biased ;)

Disney bought one of the most successful video streaming companies in the world to drive Disney+ called Bamtech, they didn't start from scratch at all - https://www.forbes.com/sites/maurybrown/2017/08/08/disney-ac...

Great feedback, thank you!

This feedback is great and very appreciated.

With the other competitors I get the point of targeting smaller customers. With that said, I think a point might be missed with what I'm trying to accomplish with this initially: Context being lost through engineers finding things. Metrics, logs, traces, etc all don't tell a root cause when its a new incident. That's usually a human putting 2 and 2 together. When that happens it can be lost never to be seen again (the trail of tears getting to the solution).

This is a super early release and this feedback was invaluable so thank you very much! There are plenty of ideas I'll be implementing in the coming weeks now that this first release is finally out of the way.

Noted, did the features page hit that marker for you if you dont mind if I ask?

I promise its a joke. I work with this gent and we were frustrated with some specs so he said he was going to make this. haha.