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.
A practical explanation of AI, AGI and ASI for engineering and product teams, covering capability, autonomy, risk, governance and real‑world impact.
Proxy and Reflect APIA 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 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.
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. SignalStore explained with real Angular trade‑offs, including scope, TypeScript ergonomics, devtools, effects, and when neither is necessary.
Model service page schema without overclaiming by matching visible content, Service data, OfferCatalog, breadcrumbs, FAQs, entities, and proof clearly.
How service pages become easier for AI search to retrieve and summarise through clear problems, visible proof, internal links, schema, and answers.
AI coding tools make code faster to produce, but technical debt still needs review, ownership, tests, documentation, and senior engineering judgement.
Diagnose traffic drops after a redesign, migration, or replatform by checking route parity, rendered HTML, redirects, canonicals, sitemaps, and schema.
How to migrate e‑commerce product and category pages to Next.js without losing SEO value, including URLs, filters, schema, canonicals, and redirects.
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.
Decide whether Shopify to Next.js is worth it by weighing storefront control, SEO, performance, checkout, apps, content workflow, cost, and risk.
Artificial superintelligence means AI that broadly outperforms humans, not just a better chatbot. What ASI means, why it matters, and what remains uncertain.
Timing attacks explained for web developers, including side channels, string comparisons, real examples, and practical defences in JavaScript.
How to design multi‑tenant Next.js architecture across routing, domains, configuration, content, caching, previews, analytics, and team ownership.