The path forward

 Throughout my life, I've often found myself choosing paths different to those taken by most of my peers. Sometimes, this was a deliberate choice, while other times it was a result of the circumstances life presented me with.

One instance of this occurred when I opted to pursue a Bachelor of Engineering in Computer Science, while most of my peers were flocking towards Electronics. Later, when many of my peers were planning to leave India, I made the decision to stay and eventually secured fulfilling roles that prevented any regrets about my choice.

Similarly, while everyone was engrossed in developing for iPhone and Symbian, I ventured into Android and published apps on that platform. I vividly recall attending a mobile conference at IIMB in 2009-2010, where during a talk, I was the only individual who solely knew Android, while others were proficient in Nokia or iPhone. Despite being advised that only Symbian and iPhone would yield financial success, I'm glad to have jumped on the Android bandwagon early on.

During my tenure at Intuit, I worked on the Android version of their TurboTax, known as SnapTax at the time. It was an incredible experience both in terms of the technology and the team. My contributions were recognized with the Technical Excellence award, which further heightened my excitement and fulfillment.

Feeling the need to challenge myself, I decided to explore the startup world and joined Adnear, which underwent several name changes over time. While working there, I managed to write a book, ticking off an item on my bucket list. The experience of working with a mix of technologies, both exciting (Redis, Kafka, etc.) and less captivating (PHP, 0MQ, KyotoDB), was truly remarkable.

Unexpectedly, instead of starting my own venture, I ended up working at Google India. My previous post detailed my experiences and learning during my time at Google, along with my decision to resign. This decision surprised many of my acquaintances, as it once again deviates from popular career choices. I'm currently considering the startup journey, and the path I'm pursuing does not involve the trendy sectors of Blockchain, AI, Electric Vehicles, or CleanTech. While this is a less conventional choice, I hope to achieve success through diligent implementation and with the support of the right partners, which I believe I have. 

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