Those 8 Questions - Question 6

The dictionary defines "faith" as belief without evidence. It
defines "stupidity" as unreasoned thinking. Is faith without
evidence a form of unreasoned thinking?

Seems so very obvious isn't it. But if you tell the same in case of Ram Setu, well it seems all too obvious. But amazingly this was the very thing I was trying oppose. I had talked about how important is faith for every Indian. So whats wrong with it. Well faith whatsoever it may be is something which you believe in and has not been disproved. Its not just a belief without evidence rather its a belief with no contradicting evidence or unexplained phenomenon justified by some means. Your faith in those changes as soon as you find a logical or scientific explanation. The planetary positions and sun being center of the solar system were explained differently before Galileo came up with the proof, that was faith. Yes at times when people start believing in faith without any logic or reasoning with the idea of harming someone else, thats when things go wrong. Its

good to have faith but we must make sure that we do not go over the top to justify it although it is wrong. A tough call at all times. But none the less you need to keep faith in people to use good judgement.

PS: This continues as a series of questions posed as explained here.

Other related posts are:

http://the100rabh.blogspot.com/2007/10/those-8-questions-question-5.html

http://the100rabh.blogspot.com/2007/10/those-8-questions-question-4.html

http://the100rabh.blogspot.com/2007/10/those-8-questions-question-3.html

http://the100rabh.blogspot.com/2007/10/are-humans-product-of-skilled-or.html

http://the100rabh.blogspot.com/2007/10/if-you-suspected-you-were-deluded-how.html

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