Programming

Compound Pattern is very common in frontend React development. What if we apply same principles to the backend development?

Understand why and when to use Factory, Singleton, Observer, and Builder design patterns

There are two groups. One who loves micro service and the other who does not. Oh, I forgot about one more group, which is kind of in between. I stand there. I want to take the advantages of having micro services at the same time don’t want to bloat the system so that advantages take the U turn.

We often get too obsessed building system that never breaks. It is equally important to expect parts of the system to break and fix it quickly!

Exceptions; the fundamental feature of most of the programming languages available today. It looks like a very simple concept. When something goes bad, throw the exception, and catch to handle it. Pretty straightforward. But believe me, this is one of the concepts I request changes while reviewing peer code

What non technical methods I eventually learned to build a maintainable and extendable project

We all started with it, if-else, a beautiful branching tool. We would have used it count less times in our past. So did I. Everything was fine till it slowly started messing up my code.

Design patterns are just a way of designing the process flow of the application so that it is easier for humans to understand, develop or enhance ...

We are used to do programming sitting alone, put headphones on, and just immerse in it. But it does not have to be that way always