Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Anthropic acquires Stainless

anthropic.com

Post reply on HN
Print view View original

341–350 of 411 posts

Re: Anthropic acquires Stainless

#341

Post by LtWorf »

perplex wrote: post #236
EmeraldSky wrote: post #216

Earlier quoted context omitted.

Why do they need the best software engineers? I thought their product was supposed to replace such roles. Yet look at the positions they’re hiring for in marketing, finance etc.: https://www.anthropic.com/careers/jobs Why aren’t they dogfooding their own products to replace such roles?

I've seen this at work. Giving Claude Code to a mediocre programmer gets you mediocre results. The really effective engineers with coding agent can accomplish a lot. Thousand monkeys...

Their whole marketing is that you need no programmer at all.

Re: Anthropic acquires Stainless

#342

Post by dgellow »

LatticeAnimal wrote: post #74
dgellow wrote: post #24

Just want to take this moment to say thank you to all the customers I had the opportunity to interact with during my time at Stainless as I expect lots of them are likely to be active in this thread. It has been an honor to work with you all and none of what happened over the past 4 years would have been possible without your trust and support

Have you considered open sourcing the SDK generator as part of the shutdown of stainless services?

The decision is up to Anthropic. As part of the transition process we created a source-available version of the codegen named stlc and everything for customers to be able to self serve without relying on Stainless SaaS (including support for custom code, and more). I cannot comment on other considerations.

If you want to know more details regarding stlc you can reach out to transition@stainless.com

Re: Anthropic acquires Stainless

#343

Post by dgellow »

TrackerFF wrote: post #339
solenoid0937 wrote: post #290

Earlier quoted context omitted.

There is a reason the EU has massive brain drain towards the US. This comes with the territory of being super unfriendly to corporations and high earners. It has its benefits too of course. Free healthcare, safety net, public transit, well maintained cities, happier median person. While the EU does a good job optimizing life for the median person, it is a nightmare for the exceptional. It should find a way to fix thi…

There's this myth that only the absolute best, the crème de la crème of European engineers will emigrate to the US to work in tech there. That is simply not true. There are tens of thousands of extremely competent engineers here that either won't, or can't leave for the US, not even if offered 10x their current salary. And to be frank, that's not only Europe. The challenge with Europe is not talent, but funding - and…

I think the core issue is really more the fragmented regulatory landscape when incorporating a business. I’m hopeful the 28th regime can help: https://the28thregime.eu/

Re: Anthropic acquires Stainless

#344

Post by dgellow »

wubwubwomp wrote: post #110

As a Stainless customer, this is frustrating! I get that most of our new customers will use AI to generate client libs. But our existing customer base depends on our Stainless generated client libs. These OpenAPI schema > client lib providers had a bit of lockin since the client libs are all slightly different. Migration's unfortunately not as easy as just switching to Speakeasy or Openapi generator w/o breaking exis…

Please reach out to transition@stainless.com, we worked on a self-service offering and the team can answer your concerns and help where possible.

Though I understand the frustration, sorry for this. If you end up looking for a competitor I would recommend fern over speakeasy, their offering is way better in my opinion (I’ve personally always seen fern as Stainless only real competition, I have lots of respect for what they’ve built)

Re: Anthropic acquires Stainless

#346

Post by galsapir »

samrus wrote: post #296
fnord77 wrote: post #266

Earlier quoted context omitted.

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

It turned API specs into ssoftware devolopment kits and model context servers. Basically connecting existing tools to AI agents so they can actually use them. They might be a big part of the reason why claude code can edit notion docs for you pretty easily

I think the question he tried to raise was "is this needed? Aren't today's / tomorrow's models well-enough equipped to deal with just OPEN API?" (idk, just if I understand the question)

Re: Anthropic acquires Stainless

#347

Post by dgellow »

rienbdj wrote: post #311

Reading what Stainless is/was - why was this a company and not an open source project?

Stainless is way more than just the codegen. If you’re curious I did write some details when responding to another comment: https://news.ycombinator.com/item?id=48191376

But Fern is a (great) Stainless competitor that went the open source way, so that could have been an option, at least for parts of it: https://buildwithfern.com/.

There is more context but I don’t think it’s my story to tell

Re: Anthropic acquires Stainless

#348

Post by wsng »

torben-friis wrote: post #257
aleph_minus_one wrote: post #254

Earlier quoted context omitted.

> I did use the word "software engineer" there The reason why I avoided this term is that in Germany, there exists a quite strict of whatx an engineer (Ingenieur) is, which is defined in the laws of many federal states (Ingenieurgesetz [engineering law]). "Ingenieur" (engineer) is a protected professional title: > https://de.wikipedia.org/w/index.php?title=Ingenieur&oldid=2... (*) Falsely claiming that you are an Ing…

Wait, does that mean that if I self describe as a software engineer on LinkedIn and get an offer by Germans id be breaking the law by accepting? If so, is this ever enforced?

The regulation is enforced if someone uses it as title, e.g “Diplom-Ingenieur Max Mustermann”. I am not aware of a court ruling for any other kind of use.

That being said, in Germany there is no official degree named Diplom-Ingenieur Softwareentwicklung, it is always Diplom-Informatiker. Also, the Expression “Softwareingenieur” is not used, the straightforward translation of software engineer would be either Informatiker (emphasizing the degree) or Softwareentwickler (emphasizing the skill).

This is no legal advice: As far as I know, the regulation is strictly about German titles, so putting “software engineer” in your LinkedIn CV is out of scope of this law.

Re: Anthropic acquires Stainless

#349

Post by thunspa »

dgellow wrote: post #330
fnord77 wrote: post #266

Earlier quoted context omitted.

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 everyt…

This is very cool, congratulations!

Re: Anthropic acquires Stainless

#350

Post by tssge »

musebox35 wrote: post #318
lionkor wrote: post #316

Earlier quoted context omitted.

I'm not who you asked, but my workflow is the same it always was, just that one tool in the process is an LLM. That's it. If I find a task to be annoying and repetetive, I use an LLM to do it, then validate it. The quality of my work only improves, and so does the speed, and I don't lose my skill over time.

I am exploring ways to document the design for the agent to read and update. What makes it difficult is the lack of structure. Spec writing is not my core skill. Schemas and APIs are easier, there are declarative ways to document them. Runtime concepts and workflows have less structure and writing prose seems so unstructured for my taste. Formal languages are too rigid. But I could not find a better way.

For me writing manpages as a spec worked well. While the format is unintuitive and tedious (at least to me), I used AI to format the manpages from my descriptions and rendered to PDF to review. Though it's been mainly useful for CLI utilities.

Once I got the manpages ready and the way I wanted, I just stored those in an empty project folder and told the agent to implement as specified in a language of my choosing.

Maybe for other development scenarios like GUI there is some "native" way to spec the project in a common format like this.

Post reply on HN