Founder vs Developer conflict!

Things you want to do and things you need to do can be different, then how you navigate through that?

Isn’t the whole purpose of starting up to do things that you love? Spoiler alert: not always. 😁

Starting to build Peerlist was a decision made by the developer within me, because working on a product and making decisions for it is super fun!

We start with just one goal, build a product that users will love. The idea that excites you is the first part of the sentence, build a product. The less thought-of and hard part of it is building something users will love. Because it needs effort! It is not always fun to take feedback, prove yourself wrong, and then iterate on it. Sometimes, it can be overwhelming.

Also, a few users later, you need to follow some processes. You can't just push something to production and feel happy about it And sometimes, this makes me wonder and miss the early days when we had the freedom to be carefree!

Though we still have that freedom, now there is also a responsibility! There is a responsibility to ship better things—not mediocre—for every user who trusted us in our carefree days.

With a growing product comes a greater sense of responsibility towards it! This includes making better decisions, marketing it, increasing sales, making progress, growing, and polishing it! Unfortunately, this isn't always something that excites a developer… but is something you have to do as a founder.

So, in a conflict between a founder who has to do less exciting things and a developer who wants to keep building, who wins the battle?

Do you know who wins? A good product :)