Software engineering

My first job was on a game engine, and for a year I wrote nothing but assembler. Years later, in a production system we rebuilt for a US manufacturer, a few lost milliseconds could cost millions of dollars. I have always considered myself an engineer first, a lesson I’ve relearned many times along the way: the programmer first delivers code, the engineer answers for what the code does in planning, building, running and maintenance, for as long as the business depends on it. AI models now write a growing share of the software, which makes everyone focus on the end result, on the business outcome.

Writing

  1. Non-deterministic AI and the illusion of control

    Some 20+ years ago I had my first big release, for a high-traffic news website. It went down so quickly that I'll never forget how shocked I was.

  2. How many IT systems can you build in one career?

    A career counted in systems, and the ECB's digital euro choice.

Press & speaking