Blog11 min read
The Real Cost of Background Coding Agents: How Token Burn Adds Up in 2026
Shows how repeated inputs and parallel agents drive token costs-and how caching, scoping, and model routing cut spend.
Read article
Blog
Notes from the build.
Field notes on shipping AI-native systems with human engineering judgement: architecture, modernisation, automation, and the tradeoffs in between.
Blog11 min read
Micro-Frontend Architecture: The Decisions That Bite 18 Months In
Why micro-frontends often fail after 12-18 months and the safe defaults to avoid it: local state, pinned deps, CI/CD, and domain teams.
Read article
Blog10 min read
When AI Agents Open Dozens of PRs: The Code-Review Burden Teams Underestimate
AI-generated PRs can overwhelm reviewers and raise defect risk; fix with ownership, CI gates, PR limits, and review caps.
Read article
Blog12 min read
Agentic BIM: How Background Clash-Detection Agents Will Reshape Construction SaaS
Always-on clash-detection agents shift BIM to event-driven workflows: triage, traceability, reduced noise, and human approval.
Read article
Blog12 min read
End-to-End AI Coding Workflow: A Production-Grade Pattern for Prompts, Error Handling, and Verification
Treat AI-generated code like a controlled engineering loop: standardize prompts, validate edits, fix exact errors, test, and gate by risk.
Read article
Blog10 min read
Antigravity vs Cursor vs Claude Code: How the Three Agentic Coding Tools Compare for Production Work in 2026
Agentic coding tools force a tradeoff: editor-first control, terminal-led safety, or orchestration-driven autonomy.
Read article
Blog12 min read
OpenCode vs Claude Code in 2026: What Changed After Both Shipped Major Releases
Control beats convenience: open, local-capable coding agents suit regulated or complex projects, while vendor-locked agents favor quick MVPs.
Read article
Blog13 min read
Zero-Downtime Modernisation: The Deployment Architecture That Makes It Actually Possible
Zero-downtime migration blueprint: parallel blue/green stacks, expand→dual-write DB changes, staged traffic shifts, and rollback rules.
Read article
Blog15 min read
When Incremental Modernisation Is the Wrong Call: The Case for Bounded Rewrites
Replace one risky subsystem instead of endless patches: use feature flags, shadowing, canaries, and strict rollback rules.
Read article
Blog12 min read
Feature Flag Rollout for Legacy Systems: The Implementation Pattern That Lets You Ship Without Freezing
Split deployment from exposure with feature flags and a dispatcher-ramp traffic safely, monitor per-path metrics, and retire flags quickly.
Read article
Blog17 min read
Dependency Graph Mapping Before a Modernisation: Why It Always Changes the Timeline Estimate
Combine static and runtime dependency mapping to uncover hidden couplings, prioritize modules, and create realistic modernization timelines.
Read article
Blog18 min read
The First-Week Legacy Audit: Exactly What We Map Before Writing a Single Line of Modernisation Code
Map stakeholders, runtime, code, routing, and tests in week one to expose hidden dependencies and lock a focused 90-day modernization scope.
Read article