Bias, Metrics and Technical Debt
Technical debt is often ignored due to bias; using clear metrics turns it into a measurable business risk, improving predictability, reducing fragility and preventing future delivery slowdown.
Retry Windows and the Limits of Idempotency
Retries hide duplicated operations your service cannot see. This piece shows why idempotency depends on the operation name you choose.
Why Early Architectural Decisions Restrict Your Future Options
Residuality is the discipline of designing boundaries that keep future options open by preventing early implementation choices from defining a whole architecture.
Software Delivery Constraints and Pipeline Throughput
Modern software delivery is not just coding. It is a seven‑stage, 32‑task pipeline. Speed gains from AI only matter when the pipeline is understood and has capacity end-to-end.
When your board wants a strategy and you have three weeks
A practical guide to producing a defensible and aligned strategy in three weeks when your board has five different meanings of the word strategy.
Measuring Reliability in the Age of AI
In a delivery system reshaped by AI, metrics are the only defence against blind risk
The Myth of Complete Specifications
A complete specification is an illusion; real systems demand incremental discovery, and SDD only works when treated as a tool inside an iterative TinySlice loop. Winston Royce knew this in 1970.
The Cost Curve of Unchecked LLM Context
LLM workflows need context, but unmanaged context growth becomes expensive and degrades results. This piece outlines how to keep usage controlled and effective.
What Python async exposes that synchronous code hides
Asynchronous IO exposes hidden waits and coupling, revealing backpressure early and making system behaviour observable.
Hiring in an AI World
AI automates code generation. Evaluate engineers on judgement, failure reasoning, and system awareness.