Articles
Engineering Practices, page 2 of 2
Engineering practices are the repeatable habits that protect quality when delivery gets busy. The writing here looks at how review, documentation, and testing support sound technical judgement, clearer ownership, and work that other engineers can inherit without guesswork.
The Hidden Cost of Replacing Juniors with AI. 
AGI vs. AI vs. ASI: What Actually Changes? AGI vs. AI vs. ASI: What Actually Changes?
A practical explanation of AI, AGI and ASI for engineering and product teams, covering capability, autonomy, risk, governance, and real‑world impact.
The Great AI Content Collapse: Why Cheap Content Makes Real Expertise More Valuable. 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 towards proof, authorship, structure, trust, and expertise.
The AI Middle Manager Problem. The AI Middle Manager Problem
AI can automate management reporting, but this article separates status theatre from judgement, coaching, accountability, and real prioritisation.
AI is Making Technical Debt Cheaper to Create. AI is Making Technical Debt Cheaper to Create
AI coding tools make code faster to produce, but technical debt still needs review, ownership, tests, documentation, and senior engineering judgement.
The AI Productivity Mirage: When More Output Does Not Mean More Value. The AI Productivity Mirage: When More Output Does Not Mean More Value
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 We Stop Treating It Like Magic. AI Will Be OK If We Stop Treating It Like Magic
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.
Next.js Multi‑Tenant Architecture. Next.js Multi‑Tenant Architecture
How to design multi‑tenant Next.js architecture across routing, domains, configuration, content, caching, previews, analytics, and team ownership.
The AI Layoff Trap: When Local Efficiency Becomes Systemic Fragility. The AI Layoff Trap: When Local Efficiency Becomes Systemic Fragility
AI automation improves productivity, but unmanaged labour displacement risks weaker demand, brittle organisations, concentrated gains, and a race to the bottom.
When Production Data Breaks a Next.js Site. When Production Data Breaks a Next.js Site
Why production data breaks Next.js sites, including CMS fields, slugs, images, relations, dates, rich text, generated routes, and validation gaps.
Responsible AI Needs an Owner. Responsible AI Needs an Owner
Responsible AI becomes real only when decision ownership, data handling, audit trails, exceptions, procurement, and support are assigned to people.
Next.js Site Broke After Deploy: A Production Triage Checklist. 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.
Enterprise AI Delivery Starts After the Pilot. Enterprise AI Delivery Starts After the Pilot
Enterprise AI delivery usually fails after the demo, when ownership, governance, support, procurement, data access, and measurement have to become real.
Agentic Systems Do Not Fix Weak Service Boundaries. Agentic Systems Do Not Fix Weak Service Boundaries
Agentic systems do not replace service design. They expose weak contracts, permissions, observability, retries, state ownership, and workflow boundaries.
Greener Software is Mostly Less Waste. Greener Software is Mostly Less Waste
Greener software starts with engineering discipline: lighter pages, fewer wasted requests, better caching, leaner CI, and deliberate use of AI compute.
Technical Debt vs. Bad Code. Technical Debt vs. Bad Code
Technical debt describes the cost of future change, not just code someone dislikes. Its origins, accidental debt, and how to make a useful case for improvement.
Bug, Defect, Issue, or Incident? Bug, Defect, Issue, or Incident?
Bugs and defects describe faults; issues track work; incidents need an operational response. How to use these labels without confusing impact with priority.