The Real Story Behind Baglihar Verdict and Pakistani Reactions

The world awaited the verdict for the Baglihar Dam. Finally it was out. Andas soon as it was out, we had Pakistani reactions. They termed this their victory. Three of their proposals were considered valid by the Neutral Committee. Here was the twist,. a day later we have Indian government officials were shouting on top of their lungs that it was a WIN-WIN for all (Straight from Stefen Covey's Bad Habits). Now how is that possible. This was supposed to be a war. In a war either its Win-Lose or Lose-Lose. Not the other way round as the Indians were claiming. So said the Pak Media. Next what you heard was this. Pakistan government backs out.. Now how is that possible. Still wondering.

Heres the real story. What happened was that the Indian claims were absolutely correct in all respects. But Indians doing something good did not go down well with the Pakistan government. So you has this new problem coming up. The World Bank's Neutral Committee was formed. It was evaluating the Indian proposal and the Pakistani objects. Pakistanis having lost most of the cricket matches to India did not want defeat for one more time. So they tried to influence the people in the Committee. They almost got through this. Just in time the RAW got the wind of this operation. Indian government promptly took counter measures. They made sure that influence was ruled out. Instead of using the Paki afeem or ganja they took the Cobra Post way. They had all the scandals of the gentlemen in video. Now the only option left for those poor neutral people was to give in to India. So they did. They informed the Pakis that 3 of their important proposals were being upheld. For the rest they did not have sufficient cause. As soon as the report was out the Minister just could not control his victorious emotions and gave the press conference hailing the report as Paki victory. Probably right that was what was meant by Paki victory, defeat in the hands of Indian. Just like Mahishasura and other demons like death at the hands of some great Gods. And the Indian counterpart were laughing all the way. They carefully gave the reaction later after laughing and studying the report carefully.


All of above is the creation of my imagination. There is no similarity to people or place, living or dead. If there is any, it be considered a coincidence.

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