Adam Jacob
👤 PersonAppearances Over Time
Podcast Appearances
And then if I change the application's port number, it would automatically reconfigure the pool. And then you can fork that into multiple dimensions and do all that stuff. And then we use all of that information in this big hypergraph of functions to deliver a user experience that's much more multiplayer and interactive in real time.
And then if I change the application's port number, it would automatically reconfigure the pool. And then you can fork that into multiple dimensions and do all that stuff. And then we use all of that information in this big hypergraph of functions to deliver a user experience that's much more multiplayer and interactive in real time.
And then if I change the application's port number, it would automatically reconfigure the pool. And then you can fork that into multiple dimensions and do all that stuff. And then we use all of that information in this big hypergraph of functions to deliver a user experience that's much more multiplayer and interactive in real time.
So we basically allow you to compose your infrastructure in a way that kind of feels like building an architecture diagram. But what it's really doing is driving this huge graph of all these complex functions and then letting you program those functions if you need to. So it's a little more like thinking about infrastructure
So we basically allow you to compose your infrastructure in a way that kind of feels like building an architecture diagram. But what it's really doing is driving this huge graph of all these complex functions and then letting you program those functions if you need to. So it's a little more like thinking about infrastructure
So we basically allow you to compose your infrastructure in a way that kind of feels like building an architecture diagram. But what it's really doing is driving this huge graph of all these complex functions and then letting you program those functions if you need to. So it's a little more like thinking about infrastructure
It's taken us five years to build it. As we're talking to each other, we're onboarding the very first production users. And there's a couple of reasons for that period of time. The big one is just that what we wanted was an order of magnitude better experience than what you could have doing it with the existing tooling. And the existing tooling is pretty good.
It's taken us five years to build it. As we're talking to each other, we're onboarding the very first production users. And there's a couple of reasons for that period of time. The big one is just that what we wanted was an order of magnitude better experience than what you could have doing it with the existing tooling. And the existing tooling is pretty good.
It's taken us five years to build it. As we're talking to each other, we're onboarding the very first production users. And there's a couple of reasons for that period of time. The big one is just that what we wanted was an order of magnitude better experience than what you could have doing it with the existing tooling. And the existing tooling is pretty good.
If you think about trying to be an order of magnitude better, there's just a lot you have to account for. I like to think about software development a little more like art than like science. Like it's a thing that we're creating because that's what we want to see. And then we're observing how other people react to it. And it's in that conversation that the art shapes itself.
If you think about trying to be an order of magnitude better, there's just a lot you have to account for. I like to think about software development a little more like art than like science. Like it's a thing that we're creating because that's what we want to see. And then we're observing how other people react to it. And it's in that conversation that the art shapes itself.
If you think about trying to be an order of magnitude better, there's just a lot you have to account for. I like to think about software development a little more like art than like science. Like it's a thing that we're creating because that's what we want to see. And then we're observing how other people react to it. And it's in that conversation that the art shapes itself.
And so the first MVPs of System Initiative started with trying to build systems where we could infer as much about the infrastructure as possible. A little like how a lot of people are trying to think about using LLMs now to try to like automate infrastructure.
And so the first MVPs of System Initiative started with trying to build systems where we could infer as much about the infrastructure as possible. A little like how a lot of people are trying to think about using LLMs now to try to like automate infrastructure.
And so the first MVPs of System Initiative started with trying to build systems where we could infer as much about the infrastructure as possible. A little like how a lot of people are trying to think about using LLMs now to try to like automate infrastructure.
We basically built these really high fidelity models with all these tunable parameters and constraints, and then would let you specify the smallest number of constraints. And then we would infer all the rest. So you could say, I need a server that can run Postgres. And we would infer from those statements that you probably meant you wanted to run it in AWS.
We basically built these really high fidelity models with all these tunable parameters and constraints, and then would let you specify the smallest number of constraints. And then we would infer all the rest. So you could say, I need a server that can run Postgres. And we would infer from those statements that you probably meant you wanted to run it in AWS.
We basically built these really high fidelity models with all these tunable parameters and constraints, and then would let you specify the smallest number of constraints. And then we would infer all the rest. So you could say, I need a server that can run Postgres. And we would infer from those statements that you probably meant you wanted to run it in AWS.
You probably wanted it to be of a particular size, right? We could infer all that behavior. And that initial MVP was pretty cool. The bummer was that in infrastructure, something works or it doesn't, usually because it's quite specific. It's not like you can just swap one thing for another most of the time.
You probably wanted it to be of a particular size, right? We could infer all that behavior. And that initial MVP was pretty cool. The bummer was that in infrastructure, something works or it doesn't, usually because it's quite specific. It's not like you can just swap one thing for another most of the time.