AI: the reality
LLMs excel at generating new artefacts but fail when asked to interpret and safely update existing ones. Their value lies in text creation tasks (research, summary, explanation, deep dives), not system modification.
Why Agentic Coding Needs Extra Staff to Stay Stable
Agentic systems generate far more code but also around 1.2 production defects per day, requiring extra fix capacity to stay stable.
Turning Problem-Explaining into Solutions
Explaining a problem to your manager is only half a solution. How to complete the circle, identify solutions, and show cost, benefits and delivery timelines.
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.
Hashgraph: a Byzantine fault-tolerant state‑driven, history‑interpreting consensus algorithm
A walk‑through of how gossip communication alone produces a single global order without leaders, coordination, or messages in a Byzantine faulty distributed system.
There is no such thing as Technical Debt
Most technical debt is not debt at all. It is the unavoidable cost of changing yesterday’s decisions to support today.
Preventing Double‑Spend: Idempotency, Internal IDs, and the Discipline of State Before Side‑Effects
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.
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.