
After trying Lerna, Nx, and plain workspaces — Turborepo changed everything with zero-config caching and parallel execution.
Setting up a monorepo can be overwhelming. After trying Lerna, Nx, and plain workspaces, I landed on Turborepo — and it changed everything.
Managing multiple apps (frontend, backend, shared packages) in separate repos was a nightmare. Dependency drift, duplicate configs, and painful deployments.
turbo.json fileI use Turborepo with pnpm workspaces. Shared packages like @repo/ui, @repo/db, and @repo/config keep things DRY across apps.
The result? 30% faster dev cycles and zero dependency conflicts.

Single-server WebSocket worked in dev. Production with load balancers? Redis pub/sub saved the day.

I've used both in production. Prisma for rapid prototyping, Drizzle when performance matters.

One docker-compose up and everything works. Database, Redis, backend, frontend. Your teammates will thank you.

Migrated from Pages Router to App Router. Server components are a game-changer but the learning curve is real.

Cache-aside, write-through, TTL strategies — practical patterns I use in production every day.

From zero to automated deployments. How I set up lint, test, build, and deploy pipelines for every project.

Discriminated unions, template literals, satisfies operator, and more. Level up your TS game.

Access tokens, refresh tokens, rotation strategies. Stop storing JWTs in localStorage.

Indexes, query plans, connection pooling, and EXPLAIN ANALYZE. Make your queries fly.