Live data from Hacker News

Anthropic acquires Stainless

anthropic.com

321–330 of 411 posts

Re: Anthropic acquires Stainless

#321

Earlier quoted context omitted.

> ... and their team is joining Anthropic to build, who knows, some dumb integration to make Hubspot data available in Claude, or something equally as boring. Fun fact, I named it "Stainless" after Stainless Steel pipes, likening ourselves to a high-end plumbing supply shop. If you look at the earliest versions of stainlessapi.com on archive.org, you'll see our original motto was "Quality fittings for your REST API".…

I can't even figure out what Stainless does (did)

[dead]

Re: Anthropic acquires Stainless

#322
post #211

Anthropic is at a place where they need the world's best software engineers, and they're willing to comp at insane levels to get them. However: You simply cannot post a Linkedin job for "Really Good Software Engineer, comp $10M+" and make any sense of the inbound applications you'll get. They're not the first to figure this out, and they won't be the last: Successfully building a company, and using that company's pro…

So basically you said: build a successful startup. Mhm...

Re: Anthropic acquires Stainless

#323

Earlier quoted context omitted.

I've also seen this. But I'll extend it to saying that giving Claude to a bad programmer gives bad results. And seeing how people use it: good programmers review output and iterate to get better output. But bad programmers simply trust the output is good: they have no ability to review it themselves and often don't try.

As a mostly non-programmer it got me a lot done. With about 5-10h over the weekend using free tier Claude and ChatGPT I managed to put together a scraper for a particular thing on a website I’m interested, grab the item images, do an initial pass with local OCR, if it hit some keywords, run openCV to crop for better OCR and dump the hits for further investigation. Nothing particularly advanced but it would have taken…

[dead]

Re: Anthropic acquires Stainless

#324
post #301

Earlier quoted context omitted.

I've also seen this. But I'll extend it to saying that giving Claude to a bad programmer gives bad results. And seeing how people use it: good programmers review output and iterate to get better output. But bad programmers simply trust the output is good: they have no ability to review it themselves and often don't try.

> giving Claude to a bad programmer gives bad results. On average, the output is still better than what a bad programmer would produce.

Maybe. A bad programmer is unlikely to get something even working so in that world nobody will depend on it because they can't even use it. A bad AI programmer (or non-programmer) can get the thing working so people will depend on it - the blast radius is now higher.

Re: Anthropic acquires Stainless

#325

Earlier quoted context omitted.

The only people "relying" on this are other startups whose VC benefactors force them to use other products under their portfolio in order to goose up their numbers.

that makes so much sense. I always wondered how the fuck did all those ZIRP era "hello world as a service" bullshit startups have any customers at all.

> I always wondered how the fuck did all those ZIRP era "hello world as a service" bullshit startups have any customers at all.

In addition to the previously mentioned collusion, a lot of the time reported users/customers are literally just fake.

See for example Sam Altman's Loopt scam.

https://www.youtube.com/shorts/C8feBk4luaE

Re: Anthropic acquires Stainless

#326

Earlier quoted context omitted.

No, the generator itself is being made source-available for previous customers

Huh! I see stlc option is added now mentioning "eligible customers", which is great news. I'm curious if we would also get GitHub action?

Reach out to transition@stainless.com, the team can provide more details and clarify eligibility. What I can say for sure is that the stlc approach comes with vanilla release–please support for the release flow (I worked on that part) and that stlc has been designed for both local and CI contexts. We also have extensive docs covering all of that

Re: Anthropic acquires Stainless

#328
post #301

Earlier quoted context omitted.

I've also seen this. But I'll extend it to saying that giving Claude to a bad programmer gives bad results. And seeing how people use it: good programmers review output and iterate to get better output. But bad programmers simply trust the output is good: they have no ability to review it themselves and often don't try.

> giving Claude to a bad programmer gives bad results. On average, the output is still better than what a bad programmer would produce.

No, it's much worse. It will take much more time to review and notice that it doesn't actually solve the problem at hand.

Re: Anthropic acquires Stainless

#329
post #274

Earlier quoted context omitted.

I can't even figure out what Stainless does (did)

Nothing (AI slop to create an unnecessary product, funded by A16Z).

well you might say that, but they got bought, so in making nothing which no one needed they did find their perfect match, anthropic, who also builds nothing and sells hot air :D.

We might have our opinions on AI and slop, but in the end of the day this was a business play and it worked out for the players. Separate that from the actual product and u can respect they did really well for themselves.

Re: Anthropic acquires Stainless

#330

Earlier quoted context omitted.

> ... and their team is joining Anthropic to build, who knows, some dumb integration to make Hubspot data available in Claude, or something equally as boring. Fun fact, I named it "Stainless" after Stainless Steel pipes, likening ourselves to a high-end plumbing supply shop. If you look at the earliest versions of stainlessapi.com on archive.org, you'll see our original motto was "Quality fittings for your REST API".…

I can't even figure out what Stainless does (did)

In short: we take your OpenAPI spec file and generate idiomatic, best in class SDKs in various languages, a highly customizable docs product (for your API and SDKs, with neat specific examples ready to be copy pasted), MCP servers, CLI clients, terraform providers.

Going further into it: the expected user experience for your team is that you create a PR in your own API repo, a GitHub action triggers builds for everything and gives you a summary via PR comments where you can directly see diagnostic feedback, see the exact diff for each SDKs, provide the commit message for your end users. Once your PR is merged we push changes to all your SDK/docs repos and prepare a release PR ready for your team to review and merge. You merge it, everything gets released to your end users.

Now what we build goes way further than that: we have a web platform where you can live edit your Stainless config file and preview your SDKs, a fairly complex diagnostic system, a really cool system that allows you to add your own custom code on top of any generated SDK directly via git — the whole repo is something you can modify to your wishes, we keep track of your custom changes and always reapply on top of the latest codegen output. And a lot of other features (I’m biased because I designed and implemented the public version but I personally really like our spec transforms, they let you apply changes to your spec file downstream, just by modifying your stainless config file).

Does that make sense?

Post reply on HN