Paul Dix

But yeah,

I think, yeah, as an infrastructure software provider, we're in a position to not be completely displaced.

Yeah.

But at the same time, like we're not, you know, we're not necessarily in the AI hype cycle, growth cycle, whatever, right?

Because what we're creating is not something, you know, that we're not on some sort of weird AI growth curve, right?

Yeah.

I mean, so there's this idea I have, and this is like a prototype that I built over the holiday, but the idea I had essentially then, which I still have now, which is, you know, before early days of InfluxDB, when I was thinking, you know, building the thing.

And one of the things I wanted to do

do was optimize for developer happiness.

I was like, if you optimize for developer productivity, make it easy for them to use, easy to create things, the software will win.

And that was informed by my experience using Ruby on Rails in the early Rails days.

I could create...

web app in a fraction of the time that you could with other frameworks.

And Ruby as a language, generally, was designed for developer ergonomics because Matz cared about creating a language that was a delight to work with.

So developer ergonomics were the thing.

And for InfluxDB, that's what I modeled.

And I took inspiration also from MongoDB because I think MongoDB really nailed developer experience early on, right?

They had a data model and a way for working with the database that just made it easier for front-end JavaScript developers to create applications on top of that database.

I was like, so that's how you win, right?

Is you focus on developer ergonomics, you make something easy to use, whatever.