
Next.js Site Broke After Deploy: A Production Triage Checklist
A Next.js production triage checklist for broken deploys, covering rollback decisions, logs, environment drift, routes, auth, CMS data, and cache.
Articles
The guides are the practical part of this archive: working explanations for a specific web development problem, written to show the decision as well as the answer. The subject varies, but the aim is consistent: enough context to use the technique sensibly rather than copy it blindly.

A Next.js production triage checklist for broken deploys, covering rollback decisions, logs, environment drift, routes, auth, CMS data, and cache.

A clear walkthrough of LeetCode Jump Game using a greedy algorithm, including why the farthest‑reach approach works and where slower ideas get stuck.

Memoisation helps JavaScript functions run faster by caching previous results. Here's a clear guide on how and when to use memoisation effectively.

Next.js Proxy replaces Middleware in v16. See what changed, how to migrate to proxy.ts, and when request‑time interception still belongs in production.

A production runbook for stale CMS content in Next.js, covering webhooks, route dependencies, ISR, cache boundaries, preview, and editor trust.

How to solve LeetCode Coin Change with dynamic programming, and why the obvious greedy approach fails on exactly the cases worth understanding in interviews.

The diameter of a binary tree is the longest path between any two nodes. I'll explain clearly how we can solve this problem using recursion in JavaScript.

A headless CMS SEO checklist covering metadata, canonicals, schema, redirects, sitemaps, preview, internal links, image fields, and publishing controls.

How to solve Course Schedule with topological sort in TypeScript, comparing Kahn's algorithm with DFS cycle detection and why in‑degrees read clearly.

Technical SEO launch criteria for Next.js migrations, covering URLs, redirects, canonicals, metadata, rendered HTML, schema, sitemaps, and recovery.

What GEO is, where it overlaps with SEO and AEO, and why crawlability, evidence, structure and practical judgement matter more than AI tricks.

The JavaScript module pattern explained through closures and private state, plus the architectural lessons it still teaches modern developers today.

Compare rendered HTML before and after a migration, checking headings, metadata, links, schema, body copy, media, crawl signals, and launch risk.

Solve Rotting Oranges with multi‑source BFS in TypeScript, treating each queue level as one minute and tracking fresh cells until spread completes.

Compare client‑side React caching, Next.js SSG, ISR and SSR caching, and Redis‑backed caches for reliable serverless data fetching and persistence.

How to diagnose traffic loss after a WordPress to Next.js migration by checking redirects, rendered HTML, metadata, canonicals, and tracking noise.

Agentic systems do not replace service design. They expose weak contracts, permissions, observability, retries, state ownership, and workflow boundaries.

A WordPress to Next.js migration checklist for URLs, content models, media, preview, redirects, metadata, schema, sitemaps, SEO, and launch checks.