Nikita Shamgunov

Since then, I started thinking, what are the key properties of a successful Postgres company? One thing I learned from the node is the team you build is the company you build. And so the second question is like, what is the right founding team to build a dominant Postgres company? And then I started engineering that founding DNA of the company.

I started calling all the Postgres committers and contributors. And then I started to think about the architecture as well. The architecture is the architecture of separation of storage and compute and therefore you need people who understand storage very well and you need to bring them into the company.

I started calling all the Postgres committers and contributors. And then I started to think about the architecture as well. The architecture is the architecture of separation of storage and compute and therefore you need people who understand storage very well and you need to bring them into the company.

I started calling all the Postgres committers and contributors. And then I started to think about the architecture as well. The architecture is the architecture of separation of storage and compute and therefore you need people who understand storage very well and you need to bring them into the company.

The company also depends on the knowledge of Postgres internals as well as the ability to plug it into the Postgres ecosystem and be accepted by the Postgres community. The two co-founders, Stas and Heike, are from the Postgres world. Both contributed to the Postgres engine. Heike is like a legend in the Postgres community and a committer for 20-some years.

The company also depends on the knowledge of Postgres internals as well as the ability to plug it into the Postgres ecosystem and be accepted by the Postgres community. The two co-founders, Stas and Heike, are from the Postgres world. Both contributed to the Postgres engine. Heike is like a legend in the Postgres community and a committer for 20-some years.

The company also depends on the knowledge of Postgres internals as well as the ability to plug it into the Postgres ecosystem and be accepted by the Postgres community. The two co-founders, Stas and Heike, are from the Postgres world. Both contributed to the Postgres engine. Heike is like a legend in the Postgres community and a committer for 20-some years.

And then Stas worked at the Postgres company, but also worked at the tech prime as well, at the largest company in a tech company in Russia at the time. And then the thing is, you need to, what Bezos says, you need to be stubborn on your vision, but flexible on the details. There's a bunch of things that we discovered on the way.

And then Stas worked at the Postgres company, but also worked at the tech prime as well, at the largest company in a tech company in Russia at the time. And then the thing is, you need to, what Bezos says, you need to be stubborn on your vision, but flexible on the details. There's a bunch of things that we discovered on the way.

And then Stas worked at the Postgres company, but also worked at the tech prime as well, at the largest company in a tech company in Russia at the time. And then the thing is, you need to, what Bezos says, you need to be stubborn on your vision, but flexible on the details. There's a bunch of things that we discovered on the way.

The first thing that we discovered, it came mostly with one of our angels. Guillermo Rauch, who is the CEO of Vercel. And through his eyes, it became obvious how important developer experience and how important serverless is in building of this company.

The first thing that we discovered, it came mostly with one of our angels. Guillermo Rauch, who is the CEO of Vercel. And through his eyes, it became obvious how important developer experience and how important serverless is in building of this company.

The first thing that we discovered, it came mostly with one of our angels. Guillermo Rauch, who is the CEO of Vercel. And through his eyes, it became obvious how important developer experience and how important serverless is in building of this company.

So if you're building a developer-first product, there's all those things across the production quality, the ability to deliver your technology in a serverless way, integrating into developer lifecycle. All of those things, they're obvious in hindsight.

So if you're building a developer-first product, there's all those things across the production quality, the ability to deliver your technology in a serverless way, integrating into developer lifecycle. All of those things, they're obvious in hindsight.

So if you're building a developer-first product, there's all those things across the production quality, the ability to deliver your technology in a serverless way, integrating into developer lifecycle. All of those things, they're obvious in hindsight.

But it takes actually a good amount of effort to build and deliver both on the technology, on the experiences, on the production quality, and on the team as well. But then as we went along, we realized that developer experience, integration with JavaScript frameworks and the JavaScript ecosystem are a big deal, and that had a big impact in the company DNA as we went along.

But it takes actually a good amount of effort to build and deliver both on the technology, on the experiences, on the production quality, and on the team as well. But then as we went along, we realized that developer experience, integration with JavaScript frameworks and the JavaScript ecosystem are a big deal, and that had a big impact in the company DNA as we went along.

But it takes actually a good amount of effort to build and deliver both on the technology, on the experiences, on the production quality, and on the team as well. But then as we went along, we realized that developer experience, integration with JavaScript frameworks and the JavaScript ecosystem are a big deal, and that had a big impact in the company DNA as we went along.

And of course, that statement, the team you build is the company you build, can be applied at every stage of the company. And so this year, the team you build is the company you build was applied to the management team. So we have now a fantastic staff team, VP of engineering coming from Mongo, VP of product coming from GitHub.