A production voice agent silently degraded due to model drift. The fix: an eval harness plus an autonomous autoresearch loop that took it from 3/14 to 13/13 passing — and 5,234ms to 1,180ms.

Fixing a voice agent using Karpathy's autoresearch blueprint

AI collapsed discovery and prototyping from weeks to hours — so clients now arrive with code, not just ideas. Here's how the tech-agency engagement, and its risks like earlier technical debt, is changing.

The Birth of the AI-Powered Agency Client

SSR and React Server Components look similar but differ fundamentally: SSR outputs request-time HTML, RSC outputs a streamable JSON-like format per component. Here's how they compare and combine in Next.js.

Server Components vs. SSR in Next.js

git bisect finds the exact commit that introduced a regression using binary search — give it a known-good and a known-bad commit and it pinpoints the culprit in ~log2(n) steps.

Hunting down regression using "git bisect"

z-index not working? Debug it visually with MS Edge DevTools' 3D View — see stacking contexts and z-index values in 3D instead of digging through the Elements panel.

Z-index not working? Debug it the modern way.

Why render React components on the server? Server Components address five client-component limits: long TTI, bundle bloat, request waterfalls, a single thread, and no server-API access.

So, why Server Components?

Lighthouse warns 'Ensure text remains visible during Webfont load'? Add font-display: swap to your @font-face so the browser shows a fallback font instead of hiding text (FOIT).

How to prevent Flash of Invisible Text with Webfonts

Lighthouse warns 'image elements do not have explicit width and height'? Add width + height attributes alongside responsive CSS so the browser reserves space via aspect-ratio and avoids CLS.

Blog