Happy Independence Day

I wish all a very Happy Independence Day. On this occasion I wish to put on some interesting info about our nation anthem
Jana gaṇa mana adhināyaka jaya hē
Bhārata bhāgya bidhātā
Pañjāba Sindhu Gujarāṭa Marāṭhā
Drābiḍa Utkala Baṅga
Bindhya Himācala ẏamunā Gaṅgā
Ucchala jaladhi taraṅga
Taba śubha nāmē jāgē
Taba śubha āśisa māgē
Gāhē taba jaya gāthā
Jana gaṇa maṅgala dāyaka jaya hē
Bhārata bhāgya bidhātā
Jaya hē jaya hē jaya hē
Jaya jaya jaya jaya hē


I think everyone knows that it was composed by Ravindranath Tagore. But it was initially composed in Bengali. Later it was translated in Hindi. It was first dung on 27th December, 1911 at the Indian National Congress session at Calcutta. Interestingly there are two versions of it which are often sung. The full or the longer version takes around 52 seconds while the shorter version with just the first and last lines of the stanza is sung for around 20sec.
The english translation of the same is
O! Dispenser of India's destiny, thou art the ruler of the minds of all people.
Thy name rouses the hearts of Punjab, Sindh, Gujarat, the Maratha country,
in the Dravida country, Utkala (Orissa) and Bengal;
It echoes in the hills of the Vindhyas and Himalayas,
it mingles in the rhapsodies of the pure waters of Jamuna and the Ganges.
They chant only thy name.
They sing only the glory of thy victory.
They seek only thy auspicious blessings.
The salvation of all people waits in thy hands,
O dispenser of India's destiny!
Victory, Victory, Victory, Victory to thee.

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