A few thoughts on the Year 2024 was for me

2024 was a transformative year, marked by both challenges and cherished moments. My journey began with my work on Gemini at Google, an experience that allowed me to collaborate with brilliant minds and contribute to innovative features. However, after several years, I felt a growing desire to make a more direct impact—a feeling I'd been contemplating as I wrote this blog post.

This prompted the difficult decision to leave Google and embark on a new venture. I co-founded a startup called Sudama Health, driven by the mission of providing affordable and accessible healthcare to people in rural and underserved areas of India. I firmly believe that telemedicine can bridge the healthcare access gap and revolutionize the Indian healthcare landscape, where a vast population faces a shortage of healthcare professionals. To achieve this, however, telemedicine needs to evolve beyond simple video calls and incorporate a range of connected medical devices to enable true transformation.

Building Sudama Health has been a phenomenal journey, filled with both validated assumptions and unexpected challenges. From interviewing and hiring doctors and nurses to managing tax filings and navigating banking complexities, we've learned a great deal. I'm thrilled that we now have a dedicated team ready to launch operations soon.

My experiment with a blog series on "Interesting Things I Learned This Week" has also been a rewarding experience. I appreciate the engagement from friends who reached out to discuss my observations, and especially those who pointed out errors. The conversations sparked by these posts are more valuable than mere "likes," and it's gratifying to share my thoughts and connect with others. I also have several smaller personal projects in progress, which I hope to complete and share. These are endeavors I couldn't pursue while employed at Google.

On a personal note, my children have been a constant source of joy and pride. Watching them discover and pursue their passions has been incredibly fulfilling. Teaching them to ride bicycles at Decathlon was a particularly fun experience. I wish I’d known the tricks of cycling when I was learning—I spent far too long falling! I also hope to take them on more vacations in 2025.

Another valuable lesson from 2024 is the unparalleled joy of connecting with old friends. I hope to nurture these connections further in the coming year. I'm deeply thankful for all the friends who made the effort to connect.

Overall, 2024 has been a year of joy, immense growth, learning, and new adventures. I'm deeply grateful for the opportunity to work on projects with meaningful impact. As I look ahead, I'm filled with excitement and anticipation. 2024 feels like a springboard, propelling me toward even greater endeavors in the years to come.

Comments

Post a Comment

Popular posts from this blog

[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

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

Image
1. Llama 3.3 -  Llama 3.3 70B model offering similar performance to the Llama 3.1 405B model, allowing developers to achieve greater quality and performance on text-based applications at a fraction of the cost.  My Take : Meta continues to impress with each new release. Their recent claim that the 3.3 70B model performs as well as the 3.1 405B model is particularly noteworthy. This rapid progress suggests that these powerful models could soon be running on personal computers or even directly in web browsers.Meanwhile, OpenAI's recent move to introduce a $200 monthly subscription for advanced access to its models raises questions about its long-term strategy. While the initial novelty factor might justify such a premium, it seems excessive, especially for users in regions like India. It's likely that we'll see highly capable language models running on mobile devices within the next six months, potentially even before desktop deployment. My experience with a Llama 3.2 1B mod...
Read more