Trends
What is actually changing in engineering
Technical write-ups of the shifts reshaping how software gets built. Each one cites the research behind it, so you can check the claims rather than take our word for them.
Spec-driven development: writing the specification as the source of truth
Spec-driven development treats the specification as the source of truth and code as its output. Where that works, where it does not, and the tooling behind it.
Context engineering: the discipline that replaced prompt engineering
Why context engineering replaced prompt engineering: retrieval quality, position bias, compaction and trust boundaries, grounded in the long-context research.
Vibe coding: what it is, where it works, and where it costs you
What vibe coding is, where it is genuinely the right call, and the measured risks — including package hallucination rates and slopsquatting attacks.
Model Context Protocol (MCP): what it is and when it is worth adopting
What MCP is, when it beats a direct integration, and the tool-poisoning research you should read before connecting an MCP server to production data.
Agentic coding: what changes when AI writes most of the code
What agentic coding changes for engineering teams — the METR and DORA evidence, where agents fail, and how to fix review before it becomes the bottleneck.
Want a read on which of these is worth acting on?
We help engineering teams work out what to adopt now and what can wait.