Coding

Check out my blog on template method pattern with an excellent example on video game NPC usecase.

Working on medium to large software systems, you realise that the real challenge is not solving complex algorithms, it’s orchestrating a system of many moving parts.

As the codebase grows and microservices multiply, designing solutions that integrate seamlessly, leverage existing components, and extend the system thoughtfully becomes increasingly difficult.

Domain-driven design is a philosophy that provides principles and patterns to address problems faced while developing complex domain models. Learn Domain driven Design:

Want to learn Domain Driven Development? Checkout my in-depth blog:

As software developers/ software architects, we often come across the question, “Why should I use your application?” Most of the enterprise-grade applications that we work on, whether greenfield or brownfield, have already been worked on or are already present.

Creating an application that answers the above questions often starts with recognising domain-specific problems requiring technical solutions. Working on medium to large software systems, you realise that the real challenge is not solving complex algorithms, it’s orchestrating a system of many moving parts.

As the codebase grows and microservices multiply, designing solutions that integrate seamlessly, leverage existing components, and extend the system thoughtfully becomes increasingly difficult.

Tackle complexity at the heart of software: Domain Driven Development

As software developers/ software architects, we often come across the question, “Why should I use your application?”

Creating an application that answers the above questions often starts with recognising domain-specific problems requiring technical solutions.

Working on medium to large software systems, you realise that the real challenge is not solving complex algorithms, it’s orchestrating a system of many moving parts.

As the codebase grows and microservices multiply, designing solutions that integrate seamlessly, leverage existing components, and extend the system thoughtfully becomes increasingly difficult.

The Template Method Pattern is a behavioral design pattern that defines the skeleton of an algorithm in a method, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithm’s structure.