Adam Stachowiak

Even if even the term, you know, and you may, this may cut deep to you potentially is Postgres compatible.

I think timescale has, has been, um,

has never been Postgres compatible.

It's always been Postgres native.

But some out there choose that Postgres compatible.

And that's because they want to do business differently.

They want to license differently.

And I think the PLG model has obviously won.

I feel as a developer, if I can't go and play with your tool,

even not so much in a free capacity, but the ability to explore it and learn it and then trust it, that's the way.

That's the way of the developer.

You got a side project, you got an itch, you want to scratch, you want to try this different thing.

And if you're not going that route, it's kind of hard to really instantiate change in your organization.

You may go from one database to another or you have an idea.

And if you can't go and explore it,

And carve it out for yourself and present it to your team.

That's the way of PLG.

That's the way of open source.

Um, yeah.

What was the original challenge you faced to even consider creating timescale?