Konrad Niemiec

We were just really focused on, oh, what is the best parts of these solutions that we can take and put together into a product most easily and deliver it to customers? But what we didn't have a great understanding about was what problems are we solving? Are we solving the problem of getting untested code out to production and being able to roll that back quickly?

We were just really focused on, oh, what is the best parts of these solutions that we can take and put together into a product most easily and deliver it to customers? But what we didn't have a great understanding about was what problems are we solving? Are we solving the problem of getting untested code out to production and being able to roll that back quickly?

We were just really focused on, oh, what is the best parts of these solutions that we can take and put together into a product most easily and deliver it to customers? But what we didn't have a great understanding about was what problems are we solving? Are we solving the problem of getting untested code out to production and being able to roll that back quickly?

Are we solving the problem of a product manager or a customer success person or a sales person or an ops person making a change to software safely? Like what problems are we actually solving with this tool and who needs this the most? And who is that initial user base? My name is Konrad Niemietz. I'm the founder and CEO of Lecko.

Are we solving the problem of a product manager or a customer success person or a sales person or an ops person making a change to software safely? Like what problems are we actually solving with this tool and who needs this the most? And who is that initial user base? My name is Konrad Niemietz. I'm the founder and CEO of Lecko.

Are we solving the problem of a product manager or a customer success person or a sales person or an ops person making a change to software safely? Like what problems are we actually solving with this tool and who needs this the most? And who is that initial user base? My name is Konrad Niemietz. I'm the founder and CEO of Lecko.

You need to really want it. It's not just about technology.

You need to really want it. It's not just about technology.

You need to really want it. It's not just about technology.

So Leko is a different take on the problems that feature flagging tools are trying to solve. And we're basing a lot of what we're doing on some implementations at big tech companies. Those systems are called dynamic configuration systems. And we're hoping to apply that to let engineers and teams that build software build their features in a way that gets out to customers as fast as possible.

So Leko is a different take on the problems that feature flagging tools are trying to solve. And we're basing a lot of what we're doing on some implementations at big tech companies. Those systems are called dynamic configuration systems. And we're hoping to apply that to let engineers and teams that build software build their features in a way that gets out to customers as fast as possible.

So Leko is a different take on the problems that feature flagging tools are trying to solve. And we're basing a lot of what we're doing on some implementations at big tech companies. Those systems are called dynamic configuration systems. And we're hoping to apply that to let engineers and teams that build software build their features in a way that gets out to customers as fast as possible.

without the complexity and the risk these downsides that traditional feature flagging tools do and frankly let engineers ship features in an imperfect world where things are changing all the time deadlines are shifting requirements are shifting you don't have the right test data you don't have the right integration tests we really hope that engineers can ship these features as correctly and safely but also as quickly as possible

without the complexity and the risk these downsides that traditional feature flagging tools do and frankly let engineers ship features in an imperfect world where things are changing all the time deadlines are shifting requirements are shifting you don't have the right test data you don't have the right integration tests we really hope that engineers can ship these features as correctly and safely but also as quickly as possible

without the complexity and the risk these downsides that traditional feature flagging tools do and frankly let engineers ship features in an imperfect world where things are changing all the time deadlines are shifting requirements are shifting you don't have the right test data you don't have the right integration tests we really hope that engineers can ship these features as correctly and safely but also as quickly as possible

So I was at Uber for a few years working on the self-driving team. We were trying to figure out how do we connect self-driving cars to Uber's network. And that was really exciting. But after a few years, I learned a lot and I wanted to be less of a cog in the machine and really make some impact. So I joined a small startup called Sisu. There, I was the 18th engineer.

So I was at Uber for a few years working on the self-driving team. We were trying to figure out how do we connect self-driving cars to Uber's network. And that was really exciting. But after a few years, I learned a lot and I wanted to be less of a cog in the machine and really make some impact. So I joined a small startup called Sisu. There, I was the 18th engineer.

So I was at Uber for a few years working on the self-driving team. We were trying to figure out how do we connect self-driving cars to Uber's network. And that was really exciting. But after a few years, I learned a lot and I wanted to be less of a cog in the machine and really make some impact. So I joined a small startup called Sisu. There, I was the 18th engineer.

And when I arrived, I was super surprised at how little of what I had at Uber was actually available to me as a regular software engineer. At Uber, I could click a button and things would just deploy. I didn't have to learn about Kubernetes or anything like that. But the one big thing that really jumped out to me was around feature flagging tooling, around dynamic configuration tooling.

And when I arrived, I was super surprised at how little of what I had at Uber was actually available to me as a regular software engineer. At Uber, I could click a button and things would just deploy. I didn't have to learn about Kubernetes or anything like that. But the one big thing that really jumped out to me was around feature flagging tooling, around dynamic configuration tooling.