Software Engineering and Technical Articles by John Kavanagh

Consultancies can unblock stalled programmes, but without ownership transfer and internal capability growth, rescue work becomes recurring dependency.

Deadline debt explained as hidden rework, incidents, technical debt, quality loss, and recovery cost when teams compress quality without recording trade-offs.

Diagnose Sass colours that survive compilation but break in Next.js production CSS when minification creates invalid mixed-unit legacy rgb() values.

Mastering Server Components in Next.js, including client boundaries, data fetching, caching, streaming, and the mistakes that make App Router code messy.

Outsourcing can accelerate delivery, but if it replaces internal ownership, companies lose platform knowledge, leverage, and the ability to change safely.

HTTP 402 was reserved for future payment systems.

Maximum Subarray and Kadane’s Algorithm explained with TypeScript, showing how a linear pass tracks current and best sums across positive and negative values.

The seniority trap happens when organisations hire experienced engineers for judgement, then deny authority, access, decision rights, and influence.

Companies talk about a high hiring bar, but weak offers, slow interviews, and vague criteria drive strong engineering candidates out long before a decision.

Machine-readable websites need more than schema.

Converting objects to query strings is essential for handling URLs in JavaScript.

Cheap engineering can shrink payroll, but it often increases rework, instability, contractor spend, supplier dependence, and total delivery cost later.

ETag and Last-Modified drive conditional HTTP requests and 304 responses.

Best practices for managing environment variables in Next.js, so secrets stay server-side and deployments do not freeze the wrong values at build time.

Approach production observability in Next.js with contextual logs, traces, release markers, client errors, cache signals, build visibility, and business data.

AI-assisted delivery can increase throughput, but cutting QA, accessibility, SEO, security, and exploratory testing in response is a costly mistake.

Underpaying senior engineers can look efficient on payroll, but often costs more through weaker hiring, slower delivery, contractor spend, and retention risk.

AI agents are starting to research, compare and narrow buying choices.

AI slop is a symptom of weak incentives, not just weak tools.

Handle faceted navigation SEO in headless commerce with URL policy, canonicals, crawl control, product data, internal links, and filter-page content.

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.

Go 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.

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.

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.

Replacing juniors with AI can weaken capability formation, mentoring, and future hiring.

Cloudflare Pay Per Crawl, AWS WAF AI Traffic Monetization and AI crawlers show crawler access becoming commercial infrastructure, not just bot control.

How to decide whether moving from Contentful to Sanity makes sense for a Next.js website, including workflow, modelling, preview, and migration risk.

A practical explanation of AI, AGI and ASI for engineering and product teams, covering capability, autonomy, risk, governance, and real-world impact.

A look into how JavaScript's Proxy and Reflect APIs work together to intercept and redefine object behaviour, including practical use cases and common patterns.

Fix Contentful preview in Next.js by checking Draft Mode, preview URLs, iframe cookies, draft data boundaries, auth, performance, and editor trust.

Solve Number of Provinces with union-find in TypeScript, comparing DFS, connected components, path compression, union by rank, and matrix scanning.

Privacy by design means building safer data handling into platforms, analytics, CRM integrations, and workflows from the start, not relying on banners later.

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

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

A practical way to debug failing Next.js builds on Vercel, from first useful error lines and environment drift to route generation and memory pressure.

Technical GEO for websites, covering indexing, renderability, entity clarity, structured data, and crawl paths without inventing an AI-only markup layer.

NgRx Store vs.