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
Interesting concept, but blue ocean as to your target customer. Would be good to see other case studies, use cases for this. Also, thank you for not another “bring your keys” product. Just abstract it away for me.
Congrats on the launch! The readme post in the blog was helpful to understand what you’re selling. Maybe you could convey those ideas more in the homepage?
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.
There's also at least the galactic orbit. There might be a very large scale orbit as well around the Great Attractor, but the jury's still bery much out on that one.
Fascinating. I think it's the first time I've heard it put that way.
For me it's more intuitive the other way around, as the "outer" loops increase in complexity (and can have additional separate loops running inside them). It also makes sense because you can always add more (meta) loops 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.
Tickets #1452, #1454, #1588. Was told "the account has been removed" on March 22nd, but I continue to receive "Last week on FireHydrant" emails specific to our org, most recently on May 29.
Yeah, there are definitely already products in this space, but we're already invested in Grafana, so it makes sense to lean in that direction, even if it meant a little custom work on our end (though it looks like that may not be necessary now)
reply