Wanna learn from the Indian Education System

As this news story suggests, the American dudes are here to study the Indian Education System. That too in Kolkatta, West Bengal. God save them. Some comments about the Education System in West Bengal is given at The Telegraph.

Clearly the students in West Bengal are overburdened by the outdated system. The text books that I studied in school were the same that were studied by my uncle 20 years ago. As far as Calcutta University is concerned, the books and syllabus has not changed since I dont know when. The text books are being passes on from father to son, provided the father was unlike me and took good care of his books. The last 25years of Communist rule has lead the state, once a shining example of educators heaven, turned into a nightmare. With all unions being dominated by the ruling Communists, it just lost its direction. It failed to see anything that the southern states of India were doing. They transformed education in India. It was the ICSE which started experimenting. Never WBHSE.

Even if they wanted to study it they should have come out to a place like Bangalore not Calcutta. How the hell can anyone really come to Calcutta to study a system which is just hopeless. Wait a minute, I see that they are learning a lot here. The only problem is that they are learning "What not to do". US is saved again.

Comments

Anonymous said…
Very well written Saurabh... :)
July 24, 2007 1:59 AM
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

[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

[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