The Retirement fund

I saw this amazing headlines from Economic Times, 70% Indians worry about outliving retirement funds. Well my first reaction was "Oh my God"Worried. Most Indians would be unable to sustain themselves once they have retired. More likely they would kill themselves or die of hunger or may need government support. But then I read the fine print there. Well its a survey by MetLife. They sure do see a big market with 70% Indians not having retirement funds. But then another truth is that 50% Indians do not have funds for the next month too. Most of them survive on a daily basis. Mind it survive not live. Then again there is still a large majority who do not invest in retirement funds.

Well that reminds me of people like my dad. He has no retirement funds. But then he does not need it either, just like my grand father. He did not need it. My dad is there after all to support him since he has retired long time back. Obviously same applies to my dad of course.

The truth also is that you invest for your life. Infact what I believe is that one should never plan to retire. Thats the most scariest thought. I know that the cost of retiring and other fundas like that. But frankly those are for loosers and ofcourse the companies marketing these Insurance plans and likes.

Will the media please refrain from giving news with such misleading and misguiding news. These work well in scaring the people and add no value to their newspaper. A paper like Economic Times is expected to add value and not filth. Is the media listening?

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