Skip to main content

Hyderabad Reloaded

When I first came to Hyderabad, I did all the touristy things that one is supposed to do when visiting a new city. I was fascinated by the old city charm that Hyderabad exudes but never had I thought that I would ever be living in this city. Strangely enough, here I am writing this, after spending more that six months living here.

Like with yours truly, you have to spend some time with this city to begin liking it. Me being a nerd, the first thing that stood out as a beacon of hope during the initial dark days here was the internet connection provided by Beam Telecom. I have lived in quite a few cities of India and believe me nowhere you will get such blazing fast internet speeds at such affordable prices. It’s a pity that Beam is just limited to Hyderabad.

Next thing that deserves a mention here is the Rajnikant-style driving practiced here. Crossing a road, travelling in an auto-rickshaw, driving a car/bike, everything here gives you an adrenaline rush! You just don’t mess with Hyderabad drivers.

Lastly my Hyderabad experience would be incomplete if I don’t mention the amazing colleagues that I work with. Its only because of them that I have learnt to play Foosball and Mafia – two amazingly addictive games, Try them at your own risk.

Finally although I hate to admit it but after some initial hesitation I have actually started liking this city. Why this Kolaveri, Hyderabad? Smile

Comments

Post a Comment

As far as possible, please refrain from posting Anonymous comments. I would really love to know who is interested in my blog! Also check out the FAQs section for the comment policy followed on this site.

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