My current thoughts on starting up



In case you are intrigued by the words, 'current thoughts' well I don't know anyone who has changed their thinking more in the last decade on various different things than me. I think it will be changing as things do and as I evolve as a person. So that's me right now.

Starting up on my own venture has been on my mind for a long long time. But it has not really taken any real shape till now. My mom still jokes that I wanted to start adda.com while in school. You know it never started. I had ever since thought of different things but never made them into real life. Closest I ever got was to get a prototype built and showcase it but then again never pushed it.

Of late I realise that I have a very crucial element missing which leaves me directionless after some time. I don't have a clear goal and mission for myself while building anything. The only goal at times is to build something. Guess builder culture is ingrained in me. So I gave myself some time to think about it.

Here is what I came up with

  1. I want to build something that is actually useful for people and not just an entertainment or a scam 😅 . Making money is not the only reason I would start anything. 'Do no evil' sounds like the best motto ever created. I don't care if it impacts 1Billion people or just 1Million, in the end all that matters to me is, did it make the world a better place and make some money for me.
  2. I want to run a sustainable business, not just a quick rich scheme. It's much harder, it's much riskier, but it's also much more satisfying IMHO. This sustainable business should in 3-5 years make for me at least 10x what I make whenever I start at a conservative level. I would prefer not to exit this business anytime but build on top of it.
  3. I want to start with friends, I want to build it with trust among folks that each of us are there for it and each other completely. We all have to be super transparent with each other. Anything else will kill it for me. My understanding is that it's going to be a tough journey but if founders don't support each other, doom is right at the door.
  4. For me, friends are more important than money. We all who start have to be on the same page on this as well. We need to respect each other. Believe in each other to do the right thing.
  5. For me technology does not matter, over the past 16 years I have built stuff over very varied technologies that I am over the reluctance to use one over the other. If I have to build anything, I will pick the tech that just works.
  6. The only advantage we will ever have is the speed of execution and speed does not come with the all wheels running but all supporting each wheel to run faster and better. That's why point 3.
  7. I believe I will try a lot of different things, a lot of different approaches and experiment quite a bit before we get the right one. Just some bias I have acquired over time. Currently it stands here.
  8. I will wear a lot of different hats based on what is required at the time. Sales, marketing, and fundraising are some areas that interest me a lot and I will get into those for my startup besides the tech and product development initially. That is if starting with friends we will be jointly working on those, else there would be no choice but to wear all the hats.
  9. I will be moving out of my comfort zone completely and might be super tough on my family as well. I have thought most things through for that to make their life unchanged for the first 3 years at the very least in case I am unable to pull through.



Maybe all this is too utopian and probably not very practical. Having written all this, I hope I can have a meaningful discussion with folks and this can be the guiding light for me.

Comments

Post a Comment

Popular posts from this blog

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more

[15th December 2024] Interesting Things I Learnt This Week

Image
1. Why you should never use !! in Kotlin - Using double-bang operator(!!) is a bad practice; multiple alternatives cover every other possible case. Using it is a hack and a shortcut that will backfire while not saving you much time at the time of writing using it. You shouldn’t use it unless you're writing a short personal script. My Take : The double-bang operator (!!)  which throws null pointer exception in Kotlin might very well be considered " Billion Dollar Mistake ." While it offers a concise way to assert that a variable is not null, I believe it's preferable to have slightly more verbose code that explicitly handles nullability and avoids potential runtime exceptions. Null pointer exceptions have plagued programmers for decades, and introducing a feature that can easily lead to them seems counterproductive. I'm uncertain whether all Kotlin linters currently check for excessive or inappropriate use of the !! operator, but if yours don't, I strongly re...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more