My Ideal Startup

Well last Sunday I again happened to be at the Open Coffee Club of Bangalore. A whole lot of interesting ideas on marketing and all were tossed up. The big question that's always in my mind was answered during this session. Yes what is my ideal startup.

I think what would make up my ideal startup would be some ideas taken from Hari and Venkat (Venkat has a startup named OutSmart, so guys be ready to expect something). Here are the something's a startup should do.

  • Be positive about your idea and more importantly show it.
  • Have a long term plan, something like 2 years. Be ready and plan up to flourish in those two years, not just survive. This should be planned before you get your hands wet.
  • Waiting for VC may not be the best bet. Keep ground realities in check.
  • More often than not the power of idea is so strong that one can loose track of customer expectations. Be firmly stitched to that ground.
  • Make employees feel that they are adding value to their resume. A startup may fail but their knowledge will make them sail ahead.
  • Be ready to refuse people rather than just recruit for the sake of it. Get only the best. A 1::500 recruit to resume ratio is not unimaginative.
  • Keep all employees aware of the best things happening. It drives the spirit to work in them.
  • Drive the team spirit by making sure that people sit in a group so that team spirit thrives.
  • Money or any kind of benefit cannot stop an employee from quitting your company. Bonds etc only bring a bad name to the company. A startup for sure cannot afford it. Instead if the employee may come back if he finds the relationship and environment worth the value. Even if he does not he will brag about his past company. This sure will bring goodwill to you and perhaps some good employees too.

I don't know about others but I sure will follow this for my startup if I ever start.

Comments

Post a Comment

Popular posts from this blog

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

Image
1. AI Makes Tech Debt More Expensive - The core argument is that generative AI significantly widens the gap between codebases with low and high tech debt. Companies with clean code can leverage generative AI to write code much faster, while companies with messy legacy codebases struggle to adopt these new tools. This widens the gap between the two codebases, making tech debt even more expensive for companies with outdated systems. My Take : Legacy systems inevitably accumulate technical debt. A common analogy for this is the state of urinals over time: missed targets lead to increasing mess, keeps pushing people away from urinals and leading to more mess in turn. AI-powered coding tools could potentially accelerate the accumulation of tech debt. However, skilled engineers can leverage AI to reduce and even eliminate it. Ultimately, AI is just a tool, and human judgment remains crucial for making informed decisions. I hope AI will be used responsibly to drive positive outcomes. 2. Make...
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

[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