Someone Has to Sign It
Accountability is the binding constraint once a retrieval-augmented system reaches production. The coda to the RAG series.
Turning rigorous research into intelligent systems.
Writing
Essays on building and governing AI systems: as the techniques mature, the binding constraint shifts to judgement, governance and accountability. Written for the people who build, run and answer for them.
Three essays that together show governance judgement, regulatory awareness and the technical-to-current synthesis.
Accountability is the binding constraint once a retrieval-augmented system reaches production. The coda to the RAG series.
Compliance is a floor, not a ceiling. What we owe the people whose lives sit inside the data, before harm arrives.
Hinton, neural networks and the long road to deep learning: what the field looked like before the data and the GPUs arrived.
What quietly fails in retrieval-augmented generation, and how to catch it.
Getting clear on the job before reaching for the architecture.
Where the errors move to once retrieval is in the loop.
Why retrieval scores look better than the retrieval is.
The limits of convenient metrics for generated answers.
When the infrastructure is the badge, not the requirement.
Retrieval opens a door; least privilege and provenance keep it watched.
The coda: who is accountable when the system is wrong.
Why adopting AI well is more than calling an API.
The opener: you bought the capability in an afternoon and budgeted for none of the years it now has to keep working. Why adopting AI well is more than calling an API.
Using a language model for a task it was never built for, in a domain where being wrong costs money.
Agents touching production systems and customer data with no monitoring, audit logs or least-privilege thinking.
Monitoring is a modelling task, not a scripting task: drift, retraining triggers and data-quality decay can't be governed by someone who doesn't know how the model works.
Where decades-old optimisation methods still run the world, and what is genuinely new.
Simulated annealing, genetic algorithms and tabu search still run much of the infrastructure around us; the frontier is how we combine them.
What a metaheuristic really is: a framework, not an algorithm, powered by memory and learning rather than randomness dressed in metaphor.
Long before the 2012 breakthrough, optimisation researchers assessed neural networks honestly rather than dismissing or overselling. Why that patience aged well.
EURO's fiftieth-anniversary review: fifty years on, the techniques are everywhere and the most interesting work is still ahead.
The same intractable problems optimisation wants to crack are the ones cryptography needs to hold. A thirty-year view of that tension.
The history, infrastructure and engineering judgement underneath today's tools, with the applied ML that puts them to work.
With the EU AI Act in force, interpretability, uncertainty quantification and lifecycle monitoring are operational requirements, not optional extras.
Replicated storage, divided computation and rising abstraction turned big data from a specialist ordeal into something ordinary.
Forecasting now takes an afternoon, yet financial data, for reasons of codependency and regime change, stays among the hardest to forecast.
From which film you might like to the quiet logic ordering much of what we read, buy and believe.
A handful of undergraduate distributions predict customer value and defection with surprising robustness. Why simple models still hold their own.
Agile corrected the real failures of older practice, but a particular kind of depth went with it, and it is worth recovering.
Compute was a budget and memory was counted. Abundance lifted those constraints, and quietly removed an awareness scarcity once made compulsory.
Without hardened libraries, databases or open source, 1990s investment banks built straight-through processing anyway.
Taught by Turing and Newman, eleven years on ciphers, a closing book from Caesar to the internet: the continuity of cryptographic security.
From plaintext Telnet to SSH and TLS: how open standards are made, and why their priorities shifted from connection to security.
Thirty years across Ada, C, C++, Java and Python: why every programmer should spend real time closer to the machine.
Externally published pieces, republished here with formatting updated for readability.
A thought-leadership article advocating inclusion and representation in AI.
How AI will reshape knowledge work in banking, from research to compliance, much as robots reshaped manufacturing.
An ahead-of-the-curve case for machine-learning adoption in banking: mine your own transaction data.
An early commentary on data-driven transformation in banking: cutting through the hype to where data creates value.