Konrad Niemiec

So I think initially we focused a little too much on scalability and I think that may have slowed us down a little bit in the long run. You never really expect everything. You can't anticipate everything once you get out there and launch. So I do think that there are things we've learned that we didn't quite anticipate for in terms of certain aspects of scale.

So I think initially we focused a little too much on scalability and I think that may have slowed us down a little bit in the long run. You never really expect everything. You can't anticipate everything once you get out there and launch. So I do think that there are things we've learned that we didn't quite anticipate for in terms of certain aspects of scale.

But I think in general, an engineer has to, especially an engineer who has worked at a big tech company, who has been taught to build for scale. I think you actually need to fight that if you're at an early stage startup and try to say, we don't actually need to make this super rounded because users might not even want that. Or this might not even be what we end up building on in the future.

But I think in general, an engineer has to, especially an engineer who has worked at a big tech company, who has been taught to build for scale. I think you actually need to fight that if you're at an early stage startup and try to say, we don't actually need to make this super rounded because users might not even want that. Or this might not even be what we end up building on in the future.

But I think in general, an engineer has to, especially an engineer who has worked at a big tech company, who has been taught to build for scale. I think you actually need to fight that if you're at an early stage startup and try to say, we don't actually need to make this super rounded because users might not even want that. Or this might not even be what we end up building on in the future.

We might rewrite this in a few months anyways. So I think fighting that has actually been a priority of mine and something that we're trying to push with the team.

We might rewrite this in a few months anyways. So I think fighting that has actually been a priority of mine and something that we're trying to push with the team.

We might rewrite this in a few months anyways. So I think fighting that has actually been a priority of mine and something that we're trying to push with the team.

So I'm most proud of the fact that I think we're approaching this problem, which I think has been solved in a very similar way. If you look out across the ecosystem, I think in a fairly novel way, and I'm very excited about that. And I'm hoping that listeners of this podcast will get a chance to look at our website and try out our free forever tier that's launching this week.

So I'm most proud of the fact that I think we're approaching this problem, which I think has been solved in a very similar way. If you look out across the ecosystem, I think in a fairly novel way, and I'm very excited about that. And I'm hoping that listeners of this podcast will get a chance to look at our website and try out our free forever tier that's launching this week.

So I'm most proud of the fact that I think we're approaching this problem, which I think has been solved in a very similar way. If you look out across the ecosystem, I think in a fairly novel way, and I'm very excited about that. And I'm hoping that listeners of this podcast will get a chance to look at our website and try out our free forever tier that's launching this week.

and we can see that instead of having an external source of truth and some system which is difficult to debug we've really met engineers where they are and given them a novel editing experience and interaction experience with a dynamic configuration or a feature flagging tool and that's what i'm really proud of is i think we've found something that our initial users are really excited about and even i think similar ideas popping up in surrounding spaces which i'm really excited about

and we can see that instead of having an external source of truth and some system which is difficult to debug we've really met engineers where they are and given them a novel editing experience and interaction experience with a dynamic configuration or a feature flagging tool and that's what i'm really proud of is i think we've found something that our initial users are really excited about and even i think similar ideas popping up in surrounding spaces which i'm really excited about

and we can see that instead of having an external source of truth and some system which is difficult to debug we've really met engineers where they are and given them a novel editing experience and interaction experience with a dynamic configuration or a feature flagging tool and that's what i'm really proud of is i think we've found something that our initial users are really excited about and even i think similar ideas popping up in surrounding spaces which i'm really excited about

So I think one of the biggest mistakes we made from our first MVP to the second was we weren't really focused on what problems we're solving through our tool. Everyone on the team had seen dynamic configuration tools work really well internally at big tech companies.

So I think one of the biggest mistakes we made from our first MVP to the second was we weren't really focused on what problems we're solving through our tool. Everyone on the team had seen dynamic configuration tools work really well internally at big tech companies.

So I think one of the biggest mistakes we made from our first MVP to the second was we weren't really focused on what problems we're solving through our tool. Everyone on the team had seen dynamic configuration tools work really well internally at big tech companies.

And 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?

And 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?

And 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?