Skip to main content

Scientifically Unscientific

It was my second year of engineering course and I was in the Electronics Communication Lab. The practical examination for the subject was going on and the external examiner was expected to arrive anytime to check our readings. I was sweating out to get correct readings for Amplitude vs. Frequency of a circuit but to no avail. May be the equipment was faulty. Out of ten readings, only two matched. Faced with the prospect of flunking the exam, I fudged the readings to produce a graph which resembled the expected one.  The only problem was that I noted down my first readings with a pen, so I had to cut them out to take down new readings. The examiner got suspicious at this and started querying me. After much arguments to convince him of the authenticity of the readings, which later turned to pleading, I was allowed to pass the exam with only the passing marks. Moral of the story : Always note down scientific readings with a pencil.

Circa 2010. The Genetic Engineering Approval Committee has tabled a report about the tests it carried out on BT Brinjals (genetically modified Brinjals). The section on protein estimation in cooked brinjal says that uncooked non-BT brinjal also tested positive for BT protein (!!) leading to speculation whether the report is fudged. The government has brushed it aside as a typo but after reading my story above, you know better.

This brings me to an important question - Why Brinjal?!!! Why not anything else? Its not like we are dying to have a genetically modified version of Baingan Ka Bhartha. It isn't even the favorite food of Indians, infact most people hate it. Now they will have a reason not eat it. It looks like a conspiracy against the humble brinjal. And the way Mr. Sharad Pawar is pushing this for approval, it will not be surprising if we hear of a Brinjal-gate in the near future.

The second big scientific mistake is the study which claimed that Himalayan glaciers will be melting by 2035. IPCC has now admitted that there was a mistake and that they were off by 300 years!! Its just another typo which made the world leaders who assembled at Copenhagen a bit ashamed on being fooled by a group of scientists.

The third big scientific mistake (and this one's revealed after 12 years) is that the Lancet report linking vaccines to autism is false. This report had led to a sharp drop in vaccination rates in both Britain and the United States and a resurgence in measles. People still are afraid to get their children vaccinated. Its now claimed that the study was conducted on only 12 children and hence not conclusive. Another case of data manipulation, if I dare say so.

What really surprises me is not that these scientists had fudged the data, but that how can they be so naive in manipulating it. May be they didn't bring a pencil with them!

My only message to these scientists is what Joey says in Friends, "If you are doing it wrong, do it right!"

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo