
The Great AI Content Collapse: Why Cheap Content Makes Real Expertise More Valuable
The AI content collapse makes cheap publishing less valuable, shifting durable content strategy toward proof, authorship, structure, trust, and expertise.
Articles
Engineering practices are the repeatable habits that help teams protect quality under real delivery pressure. Code reviews, standards, documentation, onboarding, technical spikes, testing, and sensible metrics all belong here when they make the work clearer, more maintainable, and easier for others to inherit.
Below you will find a subset of articles from my blog specifically about Engineering Practices. This is an area I have worked with for many years, and it has been a regular subject in my writing. There are nine articles collected together for you below.

The AI content collapse makes cheap publishing less valuable, shifting durable content strategy toward proof, authorship, structure, trust, and expertise.

AI can automate management reporting, but this article separates status theatre from judgement, coaching, accountability, and real prioritisation.

AI coding tools make code faster to produce, but technical debt still needs review, ownership, tests, documentation, and senior engineering judgement.

AI can inflate output without improving outcomes. This article explains why weak metrics, faster generation, and shallow review create a productivity mirage.

AI will be OK if teams treat it as real technology, not magic, with adoption shaped by judgement, skills, governance, shared access, and careful autonomy.

How to design multi‑tenant Next.js architecture across routing, domains, configuration, content, caching, previews, analytics, and team ownership.

AI automation improves productivity, but unmanaged labour displacement risks weaker demand, brittle organisations, concentrated gains, and a race to the bottom.

Why production data breaks Next.js sites, including CMS fields, slugs, images, relations, dates, rich text, generated routes, and validation gaps.

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