Jared Santo

Gotcha. Yeah. I'm in the dashboard too, and I'm looking at a different section of that same monitoring section, which is like rows. I believe rows being added, which is kind of cool because over time you can kind of see your database updates essentially deleted, updated, inserted. So there's definitely obviously activity. We're aware of that.

Gotcha. Yeah. I'm in the dashboard too, and I'm looking at a different section of that same monitoring section, which is like rows. I believe rows being added, which is kind of cool because over time you can kind of see your database updates essentially deleted, updated, inserted. So there's definitely obviously activity. We're aware of that.

I think the other things that we should pay attention to in terms of is it working for us as expected is, I would say some of that is potentially on you, Jared, and you too, Gerhard, is that we've got the idea of branching. Gerhard, I know that you're familiar with it because you demonstrated some of this last time we talked, but being able to integrate some of those futuristic, let's just say,

I think the other things that we should pay attention to in terms of is it working for us as expected is, I would say some of that is potentially on you, Jared, and you too, Gerhard, is that we've got the idea of branching. Gerhard, I know that you're familiar with it because you demonstrated some of this last time we talked, but being able to integrate some of those futuristic, let's just say,

features into a database platform. This is managed. It's serverless. We don't have to manage it. We get a great dashboard. We get the opportunity for branches. Have you been using branches, Jared? Do you need to use branches? Does that workflow not matter to you? I think that's the DX and the performance is the two things I think I care about.

features into a database platform. This is managed. It's serverless. We don't have to manage it. We get a great dashboard. We get the opportunity for branches. Have you been using branches, Jared? Do you need to use branches? Does that workflow not matter to you? I think that's the DX and the performance is the two things I think I care about.

And so the idea would be to just automate some of that, not have to go through all the steps. Still do the CLI installation like any normal user would. Correct. But maybe a neon setup script that probably populates a file with credentials or something.

And so the idea would be to just automate some of that, not have to go through all the steps. Still do the CLI installation like any normal user would. Correct. But maybe a neon setup script that probably populates a file with credentials or something.

Speaking of one password, did you notice their new SDKs? Is that, did you pay attention to their new SDKs they deployed? TypeScript, Go, a couple others for native integrations. Obviously we're Elixir, so it doesn't really matter to us, but maybe in some of the Go pipelining, I know you've probably done. Would it make sense to skip OP and go straight to Go with the SDK? Yeah.

Speaking of one password, did you notice their new SDKs? Is that, did you pay attention to their new SDKs they deployed? TypeScript, Go, a couple others for native integrations. Obviously we're Elixir, so it doesn't really matter to us, but maybe in some of the Go pipelining, I know you've probably done. Would it make sense to skip OP and go straight to Go with the SDK? Yeah.

Because OP is their CLI, right? It's same. It's not an SDK. The SDK lets you native integrate into the language.

Because OP is their CLI, right? It's same. It's not an SDK. The SDK lets you native integrate into the language.

Well, that's where my, that's where my personal angst relies. It just, it lives right there in that question. How many times, what is the pain level it's high for me?

Well, that's where my, that's where my personal angst relies. It just, it lives right there in that question. How many times, what is the pain level it's high for me?

And what should we expect to see when we type in just contribute? Is instructions or a set?

And what should we expect to see when we type in just contribute? Is instructions or a set?

I like this. I mean, I did run just in our repository. You get contribute, deps, dev, install. These are all the actions or recipes. Correct. Install, Postgres down, Postgres up, tests. And each of those have a little hashtag next to it, which is a comment, essentially, of what the recipe does.

I like this. I mean, I did run just in our repository. You get contribute, deps, dev, install. These are all the actions or recipes. Correct. Install, Postgres down, Postgres up, tests. And each of those have a little hashtag next to it, which is a comment, essentially, of what the recipe does.

So over time we can expect to see more of these just recipes if this pans out to be, you know, long term. These recipes will potentially get more and these will be a reliable way to do things within the repository.

So over time we can expect to see more of these just recipes if this pans out to be, you know, long term. These recipes will potentially get more and these will be a reliable way to do things within the repository.