🚀 Day 4 of my 30 Days of Learning Challenge

Next day iin training was all about exploring the backend — and I did that through NestJS, a progressive Node.js framework built with TypeScript.

At first, I was overwhelmed. Coming from traditional JavaScript and small backend scripts, the modular architecture of NestJS felt complex. But once I got hands-on, everything started to click.

I learned how NestJS uses:

• Controllers to handle incoming requests
• Services to contain business logic
• Modules to organize features into scalable units

The decorator-based syntax (@Controller, @Injectable, @get) was strange at first, but it gave my code clear structure and intention. By the end of the session, I had created a simple /users route that returned mock data via a service — and it worked beautifully.

What I appreciated most was how opinionated NestJS is. It guides you toward building things "the right way" — enforcing clean separation of concerns, dependency injection, and testability. These are the things that make real-world software maintainable, especially on larger teams.

This was also my first time understanding the MVC pattern not as a theory but as a practical architecture. It made me think beyond "making things work" and more about building systems that are scalable and maintainable.

💬 Question for Readers:
If you’ve used NestJS or another backend framework, what was the “aha!” moment that made it finally click for you?