Why Agentic Coding will Always Introduce Errors
LLM-centred agentic systems will always make mistakes, just like human engineers. Human-authored tests are all that can stop an agentic quality drop.
LLM-centred agentic systems will always make mistakes, just like human engineers. Human-authored tests are all that can stop an agentic quality drop.
A walk‑through of how gossip communication alone produces a single global order without leaders, coordination, or messages in a Byzantine faulty distributed system.
Most technical debt is not debt at all. It is the unavoidable cost of changing yesterday’s decisions to support today.
An idempotent service must never trust client‑supplied names. This piece shows how server‑side identity, atomic state, and UUIDv4 naming prevent double‑spend and keep distributed systems safe under failure.
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.
Retries hide duplicated operations your service cannot see. This piece shows why idempotency depends on the operation name you choose.
Residuality is the discipline of designing boundaries that keep future options open by preventing early implementation choices from defining a whole architecture.
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.
A practical guide to producing a defensible and aligned strategy in three weeks when your board has five different meanings of the word strategy.
In a delivery system reshaped by AI, metrics are the only defence against blind risk