Gerhard Lazu

Maybe that's interesting, maybe we could change some of the boot phase so that we wouldn't inject the secrets from outside the application and the application itself could get them directly. But I really want to get Elixir releases going. And once we have those, things change a little bit.

Maybe that's interesting, maybe we could change some of the boot phase so that we wouldn't inject the secrets from outside the application and the application itself could get them directly. But I really want to get Elixir releases going. And once we have those, things change a little bit.

But it's all just like maybe shuffling some code from here to here, but ultimately it will still behave the same, you know, just like you would maybe bring it into the language. So I haven't seen their latest SDKs, but I would like to check them out. That's a good one for me to look into. Okay.

But it's all just like maybe shuffling some code from here to here, but ultimately it will still behave the same, you know, just like you would maybe bring it into the language. So I haven't seen their latest SDKs, but I would like to check them out. That's a good one for me to look into. Okay.

So the tooling that Jared was mentioning to make things simpler for him, I've been thinking about it from a couple of perspectives. And I realized that to do this right, it will be slightly harder. And the reason why it's slightly harder is because I would like to challenge a status quo. The status quo is you need a dagger for all of this. Maybe you don't, right?

So the tooling that Jared was mentioning to make things simpler for him, I've been thinking about it from a couple of perspectives. And I realized that to do this right, it will be slightly harder. And the reason why it's slightly harder is because I would like to challenge a status quo. The status quo is you need a dagger for all of this. Maybe you don't, right?

So I'm trying a different approach. And the mindset that I have for this is Ken Beck, September, 2012. For each desired change, make the change easy. Warning, this may be hard. Then make the easy change. So what I've done for this Kaizen, I made that change easy, which was hard, so that I could make the easy change. How hard was it? So that's what happened. Well, let's have a look at it.

So I'm trying a different approach. And the mindset that I have for this is Ken Beck, September, 2012. For each desired change, make the change easy. Warning, this may be hard. Then make the easy change. So what I've done for this Kaizen, I made that change easy, which was hard, so that I could make the easy change. How hard was it? So that's what happened. Well, let's have a look at it.

So we're looking now at pull request 521. And 521 introduces some new tooling. But I promise it's just a CLI. And what's special about it is that everything runs locally. There's no containers. There's no Docker. There's no Dagger. Everything is local. And I can see Jared's eyebrows go up a bit because that's exactly what he wanted all this time.

So we're looking now at pull request 521. And 521 introduces some new tooling. But I promise it's just a CLI. And what's special about it is that everything runs locally. There's no containers. There's no Docker. There's no Dagger. Everything is local. And I can see Jared's eyebrows go up a bit because that's exactly what he wanted all this time.

So what pull request five to one introduces is just. which is a command runner. It's written in Rust, but it's just a CLI. And if you were, for example, Jared, or even Adam could try this, if you were to run just, in our repository at the top level, you would see, Just calls them recipes, what is possible. And the one which I think the audience will appreciate is Just Contribute.

So what pull request five to one introduces is just. which is a command runner. It's written in Rust, but it's just a CLI. And if you were, for example, Jared, or even Adam could try this, if you were to run just, in our repository at the top level, you would see, Just calls them recipes, what is possible. And the one which I think the audience will appreciate is Just Contribute.

So remember how we had like this manual step, like install Postgres, you know, get Erlang, get Elixir, get this, get that. I mean, that's still valid, right? You can still use that manual approach. Or if you run Just Contribute, it will do all those things for you running local commands. It still uses Homebrew, it still uses ASDF, but everything that runs, it runs it locally.

So remember how we had like this manual step, like install Postgres, you know, get Erlang, get Elixir, get this, get that. I mean, that's still valid, right? You can still use that manual approach. Or if you run Just Contribute, it will do all those things for you running local commands. It still uses Homebrew, it still uses ASDF, but everything that runs, it runs it locally.

And the reason why this is cool is because, I mean, your local machine, whatever you have running, it remains king. There's no containers. Again, I keep mentioning this because that adds an extra layer. And what that means, stuff like, for example, importing a database in a local PostgreSQL is simpler because that's what you already have running.

And the reason why this is cool is because, I mean, your local machine, whatever you have running, it remains king. There's no containers. Again, I keep mentioning this because that adds an extra layer. And what that means, stuff like, for example, importing a database in a local PostgreSQL is simpler because that's what you already have running.

Resolving the Neon CLI, again, it's just like a brew install. It's there and you wire things together. You don't have to deal with networking between containers. You don't have to pass context inside of containers, which can be tricky, especially when it comes to sockets, especially when it comes to special files. So I'm wondering, how will this work out in practice?

Resolving the Neon CLI, again, it's just like a brew install. It's there and you wire things together. You don't have to deal with networking between containers. You don't have to pass context inside of containers, which can be tricky, especially when it comes to sockets, especially when it comes to special files. So I'm wondering, how will this work out in practice?

And the thing which I didn't have time to do, I didn't have time to implement just db-prod-import, which would be the only command that you'd run to connect to Neon, pull down whatever needs to pull down, maybe install the CLI if it doesn't have it, and then just in your local Postgres, import the latest copy. Same thing for just dbfork, which would be an equivalent of what we had before.

And the thing which I didn't have time to do, I didn't have time to implement just db-prod-import, which would be the only command that you'd run to connect to Neon, pull down whatever needs to pull down, maybe install the CLI if it doesn't have it, and then just in your local Postgres, import the latest copy. Same thing for just dbfork, which would be an equivalent of what we had before.