rattray

Interesting! This sounds like a surprisingly hard problem to me, from what I've seen of other infra teams.

Does that mean more "support rotations" for TS compiler engineers on GitHub? Are there full-stack TS apps that the TS team owns that ownership can be spread around more? Will the TS team do more rotations onto other teams at MSFT?

Stainless | Engineers, EMs, Former Founders, GTM, Business, more | NYC & SF ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs.

When you `npm install openai` or `pip install anthropic` or `go get …cloudflare`, for example, you’re downloading code that we generated.

We’re ~3y old, ~20 people, have strong revenue, several years of runway, and great customers (including OpenAI, Anthropic, and Cloudflare). We’re backed by Sequoia & a16z.

As one of our first 20 engineers, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, and competitive salary, benefits, and equity.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone.

Want to build the future of API tooling? See more at stainlessapi.com/jobs

Stainless | Engineers, EMs, Former Founders, GTM, Business, more | NYC & SF ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs.

When you `npm install openai` or `pip install anthropic` or `go get …cloudflare`, for example, you’re downloading code that we generated.

We’re ~3y old, ~20 people, have strong revenue, several years of runway, and great customers (including OpenAI, Anthropic, and Cloudflare). We’re backed by Sequoia & a16z.

As one of our first 20 engineers, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, and competitive salary, benefits, and equity.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone.

Want to build the future of API tooling? See more at stainlessapi.com/jobs

https://physicalintelligence.company is working on this – see a demo where their robot does ~exactly what you said, I believe based on a "generalist" model (not pretrained on the tasks): https://www.youtube.com/watch?v=J-UTyb7lOEw

Not related, but because I also liked that one, I'll add:

Devil in the White City, by Eric Larson

Covers the Chicago World's Fair of 1893. Light on some of the sorts of details OP is asking for; also follows the thread of a serial killer to keep things interesting for those less interested in the business/engineering, but still good.

Stainless | Engineers, EMs, Former Founders, AEs, Business Generalists, more | NYC ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs.

Our first product is SDKs as a service. I built the codegen system at Stripe for their SDKs, and am now building a better version for everyone.

When you `npm install openai` or `pip install anthropic` or `go get …cloudflare`, for example, you’re downloading code that we generated.

We’re ~3y old, ~20 people, have strong revenue, several years of runway, and great customers (including OpenAI, Anthropic, and Cloudflare). We’re backed by Sequoia & a16z.

As one of our first 20 engineers, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, and competitive salary, benefits, and equity.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone.

Want to build the future of API tooling? See more at stainlessapi.com/jobs

I was using a mobile browser; on many mobile browsers it's hard to see/edit the URL, unfortunately.

Wish there was an example link on the project homepage. Or better yet, links to a few of the top current articles from the Reuters homepage.

Eventually consistent list endpoints!? How did they justify/explain that? Do they provide guidance on how to work around it?

> a new API version also presents an opportunity to clear out blemishes, and I expected to see more of that

Curious, what are some other Stripe API blemishes that folks would have liked to see cleaned up in a v2?

I worked on the API and SDKs at Stripe alongside Brandur, and honestly I was a little surprised to see him say that too.

I also think the underlying API has to be good for the overall DX to be good, even if these days most devs want static types and thus SDKs for any nontrivial API.

(Thanks for the kind words on the Stripe Node.js SDK btw - I do hope the world can standardize more around good SDK design patterns, just as with good REST design patterns!)

I have found the same.

FWIW this gave more entertaining but ultimately worse results than without on Claude for me, using the prompt:

> How many chickens can fit on a 747?

How big of a business is SQLite?

Belated, but especially when I see the group syntax, I wonder if this should be like a Markdoc extension or something?

How'd you get to 150?

Looks interesting. Any tips for using it effectively? What's it been most helpful with?

> I'd love to have a visual builder that creates code you can host yourself — something like retool.com but with open source and self-hosting

I believe this is the promise of AppSmith: https://www.appsmith.com/

I haven't tried it myself, curious for others' experiences

Stainless | Generalist Engineers, Customer Engineers, Full-Stack Engineers, EMs, Former Founders, Account Executives, more | NYC ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs. Our first product is SDKs as a service. I built the codegen system at Stripe for their SDKs, and am now building a better version for everyone.

When you `npm install openai` or `pip install anthropic` or `go get …cloudflare`, for example, you’re downloading code that we generated.

Next, we want to make it easy to build amazing REST APIs. REST is simple and ubiquitous, but right now it’s also messy, chaotic, and hard to get right. We’re going to build great open-source standards and tooling that bring the benefits of GraphQL (types, field selection/expansion, standards) and gRPC (types, speed, versioning) to REST.

We’re ~3y old, ~20 people, have strong revenue, several years of runway, and great customers (including OpenAI, Anthropic, and Cloudflare). We’re backed by Sequoia.

As one of our first 20 engineers, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, and competitive salary, benefits, and equity.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone.

Want to build the future of API tooling? See more at stainlessapi.com/jobs or say hi: alex at stainlessapi.com

Interesting! How does that work for nested properties?

personally I'm super excited to see this -- have been wanting something along these lines for quite some time.

note the creator did not intend for the project to be posted to hn at this time

Hursh responded elsewhere on the thread:

https://news.ycombinator.com/item?id=41606219

This looks awesome.

It was a bit hard to see on mobile - what are the hotkeys in the first demo to select the full function call?

Stainless | Generalist Engineers, Customer Engineers, Full-Stack Engineers, EMs, Former Founders, Account Executives, more | NYC ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs. Our first product is SDKs as a service.

When you `npm install openai` or `pip install anthropic` or `go get …cloudflare`, for example, you’re downloading code that we generated. (I built the codegen system at Stripe for their SDKs, and am now building a better version for everyone.)

Next, we want to make it easy to build amazing REST APIs. REST is simple and ubiquitous, but right now it’s also messy, chaotic, and hard to get right. We’re going to build great open-source standards and tooling that bring the benefits of GraphQL (types, field selection/expansion, standards) and gRPC (types, speed, versioning) to REST.

We’re ~2y old, ~15 people, have strong revenue (could choose to be profitable), and great customers (including OpenAI, Anthropic, and Cloudflare). We’re backed by Sequoia.

As one of our first 20 engineers, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, competitive salary, and a very competitive ownership stake.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone.

Want to build the future of API tooling? See more at stainlessapi.com/jobs or say hi: alex at stainlessapi.com

Is there a place this has been discussed on HN? I'm curious for the community's views on the feature.

Ex-Stripe ('17-'20) here. Agree.

Though I am under the impression that things have gotten more sensical internally over the last year or so.

Note also that the devprod team has largely been shielded from the craziness, and may still be making good decisions (but I don't know what they are in this realm personally).

facepalm – mixed up arr & cashflow as I was going to bed. thank you.

I mean, if they think they can get to 1bn ARR reasonably soon and get, say, 30x on the public markets that's already a better outcome (plus they don't have to work at Google) -- and given their growth rate, an even better multiple might be expected.

We use rye to develop the openai-python library and it's been great.