nestjs-backend-developer

Organize code by domain modules rather than by layer: each business domain gets its own module containing dto/, controller, service, and module files. Shared utilities go in common/, database code in database/, and modules must never have circular dependencies.

Use a JwtAuthGuard for authentication followed by a PermissionsGuard for authorization, applied via @UseGuards with a @Permissions decorator like 'users:read'. Store tokens in HttpOnly Secure cookies, never in localStorage, and hash passwords with Argon2id.

Yes, Drizzle integrates directly via a DatabaseService without a custom Repository layer. Use db.transaction() for multi-write operations and leftJoin or with clauses to preload relations and avoid N+1 queries.

Middleware runs earliest for logging and CORS, guards handle authentication and role checks before route execution, interceptors wrap responses and measure timing, and pipes validate parameters. Authorization belongs in guards, not middleware.

It does not apply to frontend development with React or Vue, raw Express or Fastify projects without NestJS, standalone SQL tuning, or DevOps work like Docker, Kubernetes, and CI/CD pipelines.