Writing about real-time systems, AI and shipping software
What I learn from production work: WebSockets at scale, agents and RAG, NestJS, Laravel, caching and deploys.

Watch queue depth trend, not the current number
Track queue depth over time from day one. The current number says little; the slope tells you whether you have twenty minutes or two.
Read the post
The systems I am proud of are built from boring parts
The systems I'm proudest of use Postgres, a queue and a cache with a written invalidation rule. The real engineering was in the failure handling.

Scaling 100k WebSocket connections: the reconnect storm
At 100k+ concurrent sockets the count is easy. The reconnect storm is what breaks, and jittered backoff, load shedding and resumable sessions fix it.

MCP went stateless, and that matters
The July MCP revision went stateless with OAuth 2.0 and OpenID Connect, so MCP servers can now run behind load balancers and serverless.

npm v12 blocks install scripts by default
npm v12 no longer runs preinstall, install or postinstall scripts unless you approve them, closing a common supply chain attack path.

Node.js moves to one major release a year
From Node 27, Node.js ships one major a year and every release becomes LTS, ending the odd/even split most teams already ignored.

How an endpoint got 45 percent faster with no clever code
Twenty minutes with a profiler beat a week of guessing. An N+1, a missing index and a useless cache made an endpoint 45 percent faster.

What actually breaks when AI agents go to production
Production agents fail on state, partial failure and knowing when to stop. Those are distributed systems problems, and prompts won't fix them.

Claude output is now watermarked
Claude output now carries watermarks and signed provenance by default. Tell your users, and never treat a missing watermark as proof.

Splitting a monolith: what it actually bought us
Split a monolith for failure isolation and team ownership. If speed is the goal, profile first; the cause is usually a missing index.

Handle SIGTERM or every deploy is a small outage
A Node service that ignores SIGTERM drops in-flight requests on every deploy. A fifteen-line graceful shutdown handler fixes it.

What I stopped doing by hand with AI coding tools
AI tools took over my boilerplate, regex and first-draft tests. I ship faster but learn narrower, and I'm working on the second part.

Mongo or Postgres is the wrong first question
Pick a database by your known access patterns. If you don't know them yet, pick Postgres, because it forgives wrong guesses best.

In RAG, retrieval is the product
Most bad RAG answers I've debugged were retrieval failures. Structural chunking, metadata filters and a 50-question eval set fixed more than model upgrades.

Build at night, decide in the morning
My best code comes late at night and my best decisions come in the morning, so I build at night and decide after some sleep.

The hard part of passkeys is not WebAuthn
WebAuthn was the easy part of shipping passkeys. Account recovery and deciding whether a password fallback stays took the real work.

Caching mistakes I keep debugging
Before adding a cache, decide what invalidates it, measure first, set a TTL, and cache the expensive part instead of the whole result.

When GraphQL is worth it and when it is not
GraphQL pays off when many different clients need different slices of the same data. With one web client, REST usually wins on total effort.

Laravel ships the primitives Node developers rebuild by hand
Laravel ships primitives like debounced listeners and model-scoped locks that Node teams keep rebuilding by hand. That's a culture difference.

Why I still write code as a tech lead
Leads should keep coding on the work nobody prioritizes and stay off the critical path, so their judgment stays sharp without blocking the team.

Green flags that someone is genuinely senior
Two signals I trust: the candidate brings up a decision they got wrong without being asked, and asks about on-call before the tech stack.

Use satisfies before you reach for as in TypeScript
Every `as` in TypeScript tells the compiler to stop checking. `satisfies` checks the shape and keeps the narrow type, so try it first.

At-least-once delivery means at least once
Every queue consumer eventually runs twice. Give each one an idempotency key from the message and check it before doing the work.

Auto mode made code review the last human gate
Claude Code's auto mode is now the default, so the approval prompt no longer protects you. Code review is the human check that's left.

Multi-tenancy with Laravel
One way to run a multi-tenant Laravel app: a database per tenant, a connection per database, a Tenant model, and middleware that switches connections.