NestJS: The Good, The Bad, and The Ugly

<p>In the past years, I have developed numerous applications using NestJS, which have been utilized by hundreds, thousands, and even millions of customers throughout Europe. These applications were built in teams of different sizes, including start-ups, scale-ups, and corporate organizations. From modular monoliths to event-driven microservices, GraphQL and REST were all used and developed using NestJS. But with every good aspect, there is also a bad and even an ugly part.</p> <p>In this article, I will share my thoughts after working on NestJS during this period. My goal is to provide developers, technical leads, and team leads with the tools they need to anticipate and address any potential issues that may arise while using NestJS.</p> <h1>The Good</h1> <p>I&rsquo;ve worked in teams of different sizes, with different opinions about clean code and definitions of when an application is done. It varies from company to company, from team to team, and even from person to person. Opinions of individuals in teams are often subjective, and that can make it hard to form development guidelines and coding styles. As a matter of fact, all teams sooner or later follow the same learning curve phases, as the diagram points out.</p> <p><a href="https://betterprogramming.pub/nestjs-the-good-the-bad-and-the-ugly-d51aea04f267">Website</a></p>