Skip to main content

Deals You Can't Miss

1 Year Subscription

Startup Founder Illusion

My Dream Castle
I have had conversations in the past to head the tech functions of a fledgling startup by its founders. Being part of a startup journey is a roller coaster ride, only when the basics are set right. But when even the basics aren't right, it is a definitive path to disaster, to potentially all the stakeholders involved.

I present below a distilled conversation between me and my potential co-founders, whose offers I have had politely declined in the past or had asked to revisit his/her vision for me to join on board.

Note: I present this not to brag my superiority in any way but to share my thoughts on what I think would benefit anyone in my position in evaluating such an opportunity/challenge. On the flip-side, it should also be helpful to the founders to do a re-think on their vision, if it is something like this, because it is a BIG RED FLAG to do too many things right from the word GO.

Startup Founder: Hi, we are looking badly for a CTO, interested?

Me: What is your business idea?

Startup Founder: We would solve this, this and all that.

Me: But for each of what you said you'll solve, there is already at least one startup backedup by atleast one VC that I can mention. Why are you doing all these at a time?

Startup Founder: That preciously is the point. I would promise to build all those on my own (one-stop-shop) so that my customer need not rely on those many service providers.

Me: I'm afraid you have trivialized the efforts and money that has gone into each of those endeavours by the startups and their investors. 
    I'm afraid you are wanting to do things big-bang with the deamon of death standing right in front of you.
    Even if you were to have as deep pockets as the Tatas/Mahindras/Ambanis, I would humbly suggest, you take things on -- one bite at a time. 
    It pays to focus your attention into solving one thing very well.

P.S: This story is also published in my Linked Feed.

My Popular Posts

Ten Commandments of Egoless Programming

We are nothing but the values we carry. All through my life thus far, I tried to influence people around me with the virtues I value. Thanks to some good reading habits I had inculcated, and the fortune of being in good community of peers and mentors alike, I managed to have read some real good books. This post is about the 10 commands of egoless programming in Weinberg's book. I shall explain the commandments based on my experience here. So very many decades ago, Gerald M. Weinberg authored  The Psychology of Computer Programming . In it, he listed The Ten Commandments of  Egoless Programming , which remains relevant even today for us as not just programmers but as team-members. Weinberg is regarded as a pioneer in taking a people-centric approach to computing, and his work endures as a good guide to intelligence, skill, teamwork, and problem-solving power of a developer. When they appear to inspire and instruct, we find that they can apply to just about every business area, and e

Should I buy refurbished laptop from Amazon?

This post is based on my experience with and guess it to be true on all other platforms as well. At least you can check out and verify for these pointers before you make that decision to buy renewed/refurbished laptop on Amazon with your hard earned money. I see this question propping up in several forums and on many different occasions. In the recent past, I had my 5 year old dell laptop that gave up because its motherboard failed. One of the options that I had in my mind was to re-use the HDD and the 16GB DDR4 RAM of that old laptop in the one that I purchase next as secondary.  I had come to a conclusion that it is not worth buying a refurbished/renewed laptop at all. Why? For the following reasons, most of which I see as BIG #RedFlags: You got to remember that Amazon provides a platform for 3rd party sellers to sell their products as well. So in your search for refurbished laptops you wouldn’t want to choose some random 3rd party seller who Amazon doesn’t endorse. You cou

Multi-tenant Architectures

  Multi-tenancy Application Deployment Architecture could be modeled in 4 broad ways: Separate Apps & Separate Databases Shared Apps & Shared Databases Separate Apps & Shared Databases Shared Apps & Separate Databases There is no right or wrong here. It's about choice and consequence that you should consider taking into your business context and constraints. In this post I intend to jot down a some key points to keep in mind for each of these multi-tenant architecture. These are more of quick notes for my quick reference, a cheat-sheet of sorts when I have to make choices. And I guess this can come handy to you too in your wise decision making. Separate Apps & Separate Databases Easiest to implement from development and deployment stand-point. Just automate the deployment infrastructure for every tenant for quick set-up. Most expensive of all the models from infrastructure cost stand-point. Relatively longer deployment t