Man mummified watching TV -- The Indian perspective

There was this story of an elderly gentleman having died of natural causes.
Nothing of much importance except the fact that the world came to know of his
death after almost 12 months. He still was watching the TV in full volume as he
was in moments before he died. Amazingly nobody noticed it. The main culprit was
the weather. The environment was just right to not allow the body to decompose
It seems that the electricity people too were at fault for it and an
investigation has been promptly launched in the matter. You must be wondering
why. Well the reason is that how can someone continue to get electricity when he
has not paid his bills for a long time. In this case for over a year. Well this
is not what I am writing this post.


Actually I was wondering that if this incident would have had happen in
India. While my grey cells worked over it. It came up with some interesting
things.




  1. Say instead of watching TV he would be trying to call someone - Now
    picture this, the police enter his room. They see that he is looking down at
    his cell phone. He was trying to call someone. But the call is not going. The
    cell is set to auto-redial. The persons cell was a lifetime prepaid one. And service
    provider is Hutch. The network is following, not the cell but the user
    perhaps.

  2. Option two would be holding his first pension letter. The persons age is
    70 and he just expired the day he got his first pension letter. Right after 10
    years of retirement. The excitement took his life. Though the police would
    recover the pension cheques for the next 12 months in his mails.

  3. Ditto can be the case for Income tax refund. Poor guys could not even get
    it, I think this is what is meant by 'Haath to aaye, mooh na laga'.

  4. May be he would be infront of his comp and would had been posting some
    useless scraps. When he dies, his body lies in a manner such that the keyboard
    continues to generate some useless scraps. It would be like really too much
    actually



I know this post is gross. And I have reasons to believe that it will never
happen in India. The only thing India has is its close knit culture. Its not
dead. The popularity of orkut is enough to justify my statement.

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