People get the problem we are solving and are excited for the solution.

What @jeanqasaur is building with @AkitaSoftware is worth following. A different approach, starting with not startups or earliest adopters.

We wrote before about some slightly hacky ways to create OpenAPI from things like Postman Collections, using JSON to JSON Schema converters, and a whole lot of mucking about, but thankfully these days there are far nicer solutions around. One especially smooth tool is Akita!

So excited to have been an early user! Congrats on the launch @jeanqasaur and team!!

Akita is one of the most interesting startups in the dev tools space that I’ve seen lately.

~ Conventional testing covers less and less of what actually goes wrong ~Tipping point here now => Akita & its competitors~

I was floored by the what @jeanqasaur from @AkitaSoftware, was doing with monitoring network traffic - generating API docs. #ObservabilityInTheNicOfTime

Catch @jeanqasaur if you can. Her API tool has my favorite feature: it makes developers happy and, as a consequence, raises the security posture.

Ultimately I think @AkitaSoftware is addressing a fundamental issue in our industry: our tools are at least one generation behind the systems we're building.I care about this because I want our industry to deliver value, with reasonable "quality", without chewing through people.

@AkitaSoftware is doing a great job in the dev tools world

This `akita har ingest` excites me more than I probably should, but I see it as a nice way to decouple the regular integration tests flow, producing an HAR artifact, and the API specs "discovery" step. It really opens the door to new workflows to generate API definitions.

Not sure when Akita was founded but they employ the kind of approach I used to dream about. Very cool.

scale = risk

keeping an eye on @AkitaSoftware re: modeling sw behavior.

even just for documentation - it is terrifying to me when >50% of a team’s knowledge of service behavior is stored in 6-7 senior devs’ heads

Let's be honest, #API integrations are hard, and despite all the care and testing, they'll fail at some point.

That's where @AkitaSoftware comes in to help. They analyze your API traffic and give you visibility of what's going wrong.

Check it out https://docs.akita.software/docs

I'm so excited for the partnership with Akita Software that Nick Scheiblauer has been driving.

Not only will this work help make our product and systems more reliable, it will also help third party developers who rely upon the Flickr API working predictably!

Amazing insight and a great product. Never really thought about your thought process but wondered why it took our dev team so long to integrate certain APIs when apples to apples, should be similar.

Akita looks like a very good idea. Been building dev tools and APIs for 15 years. This looks super useful.

Will be watching to see where this goes.

So much goodness in this podcast featuring @jeanqasaur! "Take software and shake guarantees out of it"... And focusing on the #API layer in modeling the system is the embodiment of the Maier/Rechtin heuristic, "the greatest leverage in systems architecting is at the interfaces"

@AkitaSoftware is Putting the Fun Back into Programming