Blogs

Serverless is a paradigm that lays its foundations on the fact that "We don't have to provision and manage servers". Let's begin our serverless journey which starts with building a serverless application. After we have built an application we will proceed with testing it using LocalStack and finally deploying it using AWS CDK

We often have a lot to share with people, this could be our learnings, our opinions and our experiences. There are times when we feel the need to get our ideas validated or get feedback from people. These are definitely some reasons to invest in blogging and connect with community.

A domain-specific language (DSL) is a computer language specialized to a particular application domain. This is in contrast to a general-purpose language (GPL), which is broadly applicable across domains. There are a wide variety of DSLs, ranging from widely used languages for common domains, such as HTML for web pages, down to languages used by only one or a few pieces of software. Let's explore DSL in Kotlin together.

There is no doubt that Java has enjoyed a superior position when it comes to programming languages and is considered as one of the most important languages for development. However, there have been a number of languages developed on top of the JVM like Kotlin. After working on the "data-anonymization" project I realized that there are things that Java should consider importing from Kotlin.

This article is in continuation with the previous article "Let’s define Legacy code" where we defined Legacy code. Let's understand "Broken Window Theory" and add a new feature to Legacy code.

I have been having sleepless nights trying to add features in the code that we acquired from other company. I am dealing with the purest form of Legacy code. I am having a real hard time dealing with tangled, unstructured code that I have to work with, but I don’t understand a bit. Legacy code!. Let's understand what is Legacy code.