George Hadar

Building SDKs by hand is a significant investment and a lot of large companies might pour a lot of money into that effort to create something that's like approaches good developer experience. And then another group of a more growing group of companies will rely on tooling like code generators.

Building SDKs by hand is a significant investment and a lot of large companies might pour a lot of money into that effort to create something that's like approaches good developer experience. And then another group of a more growing group of companies will rely on tooling like code generators.

And so they're very interested in, like, once you make the decision to use a code generator, you're kind of forfeiting some of your own opinions and what you think a good developer experience is because you're going to delegate that to a code generator to give you an SDK that you think users will enjoy using.

And so they're very interested in, like, once you make the decision to use a code generator, you're kind of forfeiting some of your own opinions and what you think a good developer experience is because you're going to delegate that to a code generator to give you an SDK that you think users will enjoy using.

you

you

The reality is the larger your API becomes, the more you'll want to support users that want to use your API. And to do that, your instinct will be to ship a library, a package, and what we've been calling an SDK. There's a lot of effort involved in taking an API that lives in the world and creating a piece of software that can talk to that API.

The reality is the larger your API becomes, the more you'll want to support users that want to use your API. And to do that, your instinct will be to ship a library, a package, and what we've been calling an SDK. There's a lot of effort involved in taking an API that lives in the world and creating a piece of software that can talk to that API.

The reality is the larger your API becomes, the more you'll want to support users that want to use your API. And to do that, your instinct will be to ship a library, a package, and what we've been calling an SDK. There's a lot of effort involved in taking an API that lives in the world and creating a piece of software that can talk to that API.

The reality is the larger your API becomes, the more you'll want to support users that want to use your API. And to do that, your instinct will be to ship a library, a package, and what we've been calling an SDK. There's a lot of effort involved in taking an API that lives in the world and creating a piece of software that can talk to that API.

Building SDKs by hand is a significant investment and a lot of large companies might pour a lot of money into that effort to create something that's like approaches good developer experience. And then another group of a more growing group of companies will rely on tooling like code generators.

Building SDKs by hand is a significant investment and a lot of large companies might pour a lot of money into that effort to create something that's like approaches good developer experience. And then another group of a more growing group of companies will rely on tooling like code generators.

And so they're very interested in, like, once you make the decision to use a code generator, you're kind of forfeiting some of your own opinions and what you think a good developer experience is because you're going to delegate that to a code generator to give you an SDK that you think users will enjoy using.

And so they're very interested in, like, once you make the decision to use a code generator, you're kind of forfeiting some of your own opinions and what you think a good developer experience is because you're going to delegate that to a code generator to give you an SDK that you think users will enjoy using.

Bye, friends.

Bye, friends.