Fixing Render-Blocking Resources and Layout Shift in a Next.js Site
Every Next.js site I audit has the same four problems. They are not mysterious, and none of them require a rewrite. Here is the fix for each, with the reasoning.
Long-form, original articles on the things I build and the trade-offs behind them — Ruby on Rails, React and Next.js, PostgreSQL, AI voice agents, workflow automation, and system design.
Subscribe via RSS →Every Next.js site I audit has the same four problems. They are not mysterious, and none of them require a rewrite. Here is the fix for each, with the reasoning.
Most Rails apps do not hit a wall because of Ruby. They hit a wall because of the database, unbounded background work, and requests that do too much. Here is the order in which I fix those things.
Lead discovery, enrichment, a voice call, qualification, and CRM storage. Each stage is easy. The hard part is the seams between them, and that is where most automations quietly fail.
A RAG demo is an afternoon. A RAG system you can trust in production is a retrieval problem wearing an LLM costume. Focus on retrieval and the answers take care of themselves.
Payroll has no tolerance for a retry that pays someone twice. The engineering discipline it demands — idempotency, immutability, auditability — makes every other system you build better too.
The right stack is the one that gets your product to a paying customer fastest without painting you into a corner. Sometimes that is Rails. Sometimes it is Next.js. Often it is both.