Thought

As per my blogging platform, this is my 100th blog post. In this post, I would like to reflect on my writing journey and pen down my thoughts on writing. While the scope of impact of writing goes beyond one's professional career, I will try to limit it

This post focuses on yet another incident from my college days. It was the early 2000s, and SOAP (Simple Object Access Protocol)- based services were emerging. When most of the solutions were technology/ programming language specific, integrating multiple solutions was difficult. With SOAP-based web services integration, programming languages/platform-agnostic

In a previous post, I mentioned how I happened to land in JUnit while I was trying to find implementations of design patterns. In this post, I will talk about how I could take that test automation to the next level by practising Test-Driven Development (TDD). I first learned about

During my college days, "Design Patterns" was one of the topics that caught my attention. It wasn't part of our curriculum. The aspect of design patterns that mainly seemed very attractive to me was that by using them, a developer with less experience might be able

I have already written about the problems with the tech jargons in general here, and here. This post is on a very particular jargon CI/CD. The software developers' community learned about this excellent practice from the book "Continuous Delivery", authored by Dave Farley and Jez Humble.

Previously, I had written about how Jargons are not very effective in the IT industry. You might need that context to understand what I will discuss here. I saw similar concerns shared by many professionals from the industry. For example, one post talked about how people use jazzy titles such

One of the travel vloggers I occasionally watch recently started a new venture - an E-commerce service for unique traditional products from rural areas. In one of the videos, he mentioned that his website had crashed on launch day. He claimed the crash was due to the high load. It

Back in my college days, I had studied the "comment ratio" metric in my Software Engineering class. It was still in use when I joined the industry, though nobody on my team gave it much importance. Comment Ratio is the ratio of the number of lines of comment

This time, it is a story from my college days. By this time, I had owned a PC for about nine months. I had learned a few things from my experiences and failures. I was eager to offer these bits of advice to my classmates, of course, for free. I