
Everyone Wants the Best Engineers. Fewer Companies Want to Pay for Them
Almost every technology company says that it wants the strongest engineers...
Articles from more than two decades of building, rebuilding, debugging, and leading web projects.
Some are practical development notes; others are longer pieces about the decisions and trade‑offs that determine whether modern web platforms hold together in production. You can also browse articles by category.

AI agents are starting to research, compare and narrow buying choices. Websites need to serve autonomous evaluators before human visitors arrive.

AI slop is a symptom of weak incentives, not just weak tools. This article links generic output to shallow briefs, poor review, and volume‑led metrics.


Platforms can speed delivery, but cutting internal capability too far can turn efficiency into lock‑in, weak negotiating power, and expensive migrations later.

Right to Represent agreements for UK contractors, covering recruiter pressure, duplicate submissions, hybrid working changes, and safer wording before signing.

try, catch, and finallyGo beyond basic try/catch in JavaScript with finally, custom errors, async error handling, testing, user‑facing failures, and defensive‑code traps.

Slow Gatsby builds need a clear choice: optimise plugins, data, and images in place, or move to Next.js when publishing and cache limits justify it.

AI search creates visibility that is not just a ranking, click or citation. Sites need to be retrievable, quotable, attributable, and comparable by machines.

AI programmes are often adopted tactically, without enough governance for supplier risk, data exposure, quality, workforce impact, or board accountability.

Audit third‑party script cost across GTM, consent tools, analytics, experimentation, and personalisation, without breaking measurement or business workflows.

As AI reduces friction in implementation, the value of architecture, review, domain judgement, mentoring, and failure analysis rises rather than falls.

A practical Gatsby to Next.js migration checklist covering routes, data, rendering, plugins, images, redirects, preview, sitemaps, and SEO validation.

Automation can save labour, but it also creates monitoring, exception handling, vendor, governance, and security costs that many business cases ignore.

A practical Contentful to Sanity migration checklist for Next.js sites, covering schemas, references, preview, redirects, metadata, and SEO checks.

SEO best practices in Next.js, with a sharper focus on Core Web Vitals, stable layouts, lighter bundles, metadata, and real user measurement for search.

Google's old exchange was simple: crawl the web and send traffic back. AI search weakens that bargain by answering more journeys before the click.

Debug stale Next.js App Router pages with cache tags, revalidation paths, CMS webhooks, preview freshness, dependency graphs, and simpler cache contracts.

Contentful to Sanity migration risks for Next.js sites, including models, references, rich text, preview, metadata, redirects, and launch checks.

AI knowledge retrieval can weaken organisational memory when summaries hide context, dissent, incident history, product reasoning, and uncertainty.

Why CMS preview belongs in the migration plan for Next.js sites, covering draft state, auth, cookies, iframes, cache invalidation, and governance.
