I’ve been building systems commercially for 37 years. In that time I’ve worked across enough contexts to have opinions about what generalises and what doesn’t.
Some of the systems I’ve built managed portfolios exceeding $10 billion for AAA-rated investment banks in the US and Europe. That work required a certain rigour: external audits, penetration testing, the kind of scrutiny that comes with other people’s money.
Some of the software I wrote over 15 years ago is still running unchanged in production today. Other systems I’ve built have handled 10 million unique visitors per month. I’ve seen what survives and what doesn’t, and usually why.
More recently, I’ve been building systems using AI coding tools. Not advising others on it. Building, myself, end to end. The results are live and in production. If you’re curious about the quality, I’m happy to demo them.
I’ve also led engineering teams through this transition. In one PE-backed business, we measured a 73% productivity improvement across a team of 50. That number came from story points delivered per resource, adjusted for rework. Imperfect, but the delta was large enough to be meaningful.
I’m not selling a course. I’m not promoting a book. I’m a practitioner writing about what I’m seeing, for people who need to make decisions about it.
I do take on consulting and hands-on projects. If that’s relevant to you, the rest of this site explains how I work.