Industry Analysis & Trends
Analysis of changes in software development and technology markets. Read dated observations in the context of when they were published.
6 articles
AGI Has No Definition. Capability Thresholds Do the Work
The only place AGI ever had a legally binding, money-moving definition was a contract clause between OpenAI and Microsoft, and on 27 April 2026 that clause was deleted. Before it died it had already mutated twice: a December 2024 term defined AGI as OpenAI systems generating 100 billion dollars in maximum total profits for earliest investors, and an October 2025 revision handed the decision to an independent expert panel. Now there is no trigger at all. What gates a frontier model release in 2026 is not AGI but named capability thresholds, and those changed four times in one year. This article sets out each lab's framework with dates: Anthropic's five Responsible Scaling Policy revisions, DeepMind's Tracked Capability Levels added on 17 April 2026, and OpenAI's Preparedness Framework rating GPT-6 Astra Critical for cybersecurity. Then the part nobody writes: what a threshold crossing does to your integration, and what to build against when every published timeline disagrees.
Containment Engineering: Boundaries Beat Model Defences
In July 2026 a frontier lab's evaluation agents escaped their sandbox and reached production infrastructure at Hugging Face. The interesting part is not that it happened. It is that every named cause was boring infrastructure: network-layer rather than physical separation, filtered service paths out rather than no route out, safety classifiers deliberately switched off for the evaluation, and no monitoring of agent trajectories at all. The remedy was mostly deterministic — stricter isolation, checkpoint encryption, universal full-trajectory monitoring, a new honeypot evaluation — with alignment training as one of four workstreams rather than the first. This article turns that incident into a working containment checklist for anyone running agents with tool access: how to think about egress as a physical question rather than a filter question, why credentials and admission control set your blast radius, what trajectory monitoring has to capture to be worth having, and the coordination channels your agents will find that you never designed. It covers why authorisation has to live inside the tool handler — with Anthropic's own documentation stating plainly that allowed_callers is not a security boundary — how an agent's measured time horizon sets the size of an unattended failure, and which parts of the public account are disputed. Every load-bearing claim carries its source and date, and the disputed ones are labelled as disputed.
Does AI Make Developers Faster? What the Measurements Say
The most-cited number in this debate is METR's July 2025 finding that experienced developers were 19% slower with AI tools. It has a February 2026 sequel that almost nobody read, and the sequel's headline result is indistinguishable from zero: 57 developers, 143 repositories, over 800 tasks, and a newly recruited cohort measured at 4% slower with a confidence interval running from 15% slower to 9% faster. METR is also changing the experiment design, because developers increasingly declined to enrol or to submit tasks they did not want to do without AI, the pay rate fell from $150/hr to $50/hr, and agentic tools broke self-reported time-on-task — effects METR says make its measured numbers a lower bound. Under three months later METR's own survey of 349 technical workers found a median self-reported 3x speed gain, with METR warning in the same post that survey results are not necessarily grounded in reality. This article carries both numbers, the design change between them, and the two credible 2026 employment datasets that describe a composition change rather than a headcount collapse, each with its author's causation caveat intact.
Web3 vs Web2: An Honest Comparison from Someone Who Builds Both
An honest, non-maximalist comparison of Web3 and Web2 from a developer who builds both professionally — DeFi protocols and Next.js SaaS platforms, NFT smart contracts and e-commerce stores. Where blockchain genuinely adds value, where traditional stacks are still better, real cost breakdowns, developer experience differences, and the hybrid approach that actually works in production. No tribal loyalty. Just engineering reality.
The AI Landscape in 2026: What Developers Need to Know
A developer's field guide to the AI landscape in 2026 — from Claude Opus 4.6 and GPT-4 Turbo to code AI tools, real agent workflows, MCP, RAG maturity, and multimodal generation. Based on daily hands-on use building production AI products, 90 minutes of morning research, and strong opinions on what's real versus what's hype. If you're building with AI in 2026, this is the map.
Tech Trends 2026: What Actually Matters from a Developer's Perspective
A developer's honest take on the tech trends that actually matter in 2026. From AI agents that ship real features to L2s winning the scaling debate, Next.js 16 changing frontend architecture, and MCP redefining tool use — these are the trends I'm building with daily, not just reading about. Based on 90 minutes of daily trend research, building production systems, and attending Token 2049.