Adrian | JavaScript Mastery

NEW VIDEO: NestJS Full Course for Beginners in 2026 | Build a Production-Ready API 🚀 You've been building backends with Express for a while. But every job description now says #NestJS, and every modern tutorial assumes you already know it. The good news? Your Express knowledge isn't wasted, it's a head start. This video is in two parts. First, a full NestJS crash course: modules, controllers, providers, dependency injection, pipes, guards, the whole execution pipeline. Everything that feels strange about NestJS will click. Then we build a real project together, a production-style Hackathon API. The kind of backend you can actually put on a resume. Tech Stack: - @nestframework - @prisma for the DB - @better_auth - @arcjet for security - And more If you know Express, you're closer to NestJS than you think. Grab a coffee and let's dive in! → jsm.dev/nestjs-twitter…

@El_Yas_ Working on a course right now!

@jsmasterypro Thank you Adrian, is it possible to create a tutorial about this to learn how to use it like you do ?

Every AI coding failure comes down to one thing: the agent made a decision you never made. It picked the auth provider. Invented a data model. Wrote its own API client instead of using yours. I spent 9 months building a workflow around one rule: every decision lives in the repo, not the chat. Today it's open source, go break it: github.com/JavaScript-Mas…

What do you prefer for a community nowadays?

Ever wondered why #NestJS scales so gracefully? 🚀

One mental model for the #NestJS request pipeline: Middleware → Guards → Pipes → Controller → Interceptors → Response Each stage has one responsibility.

This talk goes over how what it means to be a developer has completely shifted during the span of this year and how you can learn the principles of agentic engineering to stay ahead

Handling incoming request data in #NestJS is incredibly clean thanks to parameter decorators.

Architecture decisions made late become refactors.

Added another window

Let the testing begin! testing the final versions of agentic engineering workflows I've been building over the last few months

Spent 4.5 hours testing two agentic workflows side by side. The uncomfortable takeaway: the way we build on YouTube isn't how you'd build in production. That gap is the whole reason for the course.

Is this the missing piece in your backend dev skills?

Hot take from today's build: your architecture decision records don't need to be readable by humans anymore. The agent writes them. The agent reads them. You just review and say build.

Ran two agent workflows on the same app. Compared the auth. One enforced its invariants in the database. The other in application code. One is structural. The other is disciplined. Structural wins. A forgotten function call can't corrupt state that a unique index guarantees.

A simple rule for #Nestjs backend architecture: - Controllers handle HTTP. - Services handle business logic. Each layer should have one responsibility.

Rule of thumb: never paste anything into your agent that you wouldn't want it to extract later through conversation. Pass your ENVs manually. Every time.

@heyvishal_ I've spent the last 6 months building my own, releasing soon

@jsmasterypro what do you use ? I have been wanting to create a workflow that makes sense for me. Is there any resource you'd recommend ?

Using a proper Agentic Engineering skills workflow after months of manually prompting the agent literally feels like magic. Takes more time but you get predictable, scalable, senior-level code architecture and an app which doesn't feel like vibe coded garbage.

The harness is 80% of an AI agent's power. The model is the other 20%. Most people obsess over the wrong 20%. By harness I mean the skills you give it and the workflow you run them in.