Skip to main content

What do you Like?

Roll over wheel, the greatest invention in the history of mankind is now the Facebook's humble "Like" button. The creators of this button would never have thought that it would lead to such mind-boggling revenue and precious data generation for Facebook. Nor would they have thought that it would be used for anything else other than showing your approval for somebody's status message or link.

The Like button now encompasses all the colors of emotions; love, jealousy, anger, frustration; you name it. There are various websites urging you to "Like A Like" completely oblivious of Shakespeare turning in his grave on hearing this. The Like button enables you to deconstruct a person's entire psyche if you go through his/her likes. It has served as tool for flattery (in case of your boss) or impressing (a boy/girl). 

Some likes are philosophical - "I want my lyf 2 b a book so dat i can tear those pages whch i dnt want". Never mind the fact that no one would in their right mind would consider anything written in such SMS language to be serious. Nevertheless, an entire industry has spawned around these likes with people flocking there to pour their hearts out. In a sense, Facebook thrives on human misery, which is cool for any website to do!

Facebook's Like still has a long journey ahead with the clamor for a "Dislike" button. With Facebook setting up its shop in India, it seems India will now be seriously "liked" by Facebook.

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