Book
- Turning a web page into a book: pagination, page turns and fullscreenMy book is HTML. I wanted it to read like a book: real pages, a page turn, fullscreen that survives the next chapter, and a front page you can always get back to. How the reader measures pages in the browser, and what it costs.
- Editing 80,000 words: volume in parallel, correctness by machine, judgment by meHow I ran a full reader-first edit of a 17-chapter technical book with AI agents, without losing a code sample or a diagram. One brief, nine batches, a validator that compares every file against the original, and a human read at the end.
- Write for the reader, not the auditorTechnical writing drifts into a defensive voice: passive, long, careful, addressed to nobody. I rewrote my 80,000-word book against nine rules and measured the result. Sentences got shorter, boxes got smaller, and the reader finally got addressed.
- Why the title says MBSE for AI, and why I nearly flipped itMonths after naming my book, I could not remember why it read "MBSE for AI" and not the other way round. Working it out again gave me a simple test for naming any AI initiative: put the thing you are changing first.
- Why I wrote a book: MBSE for AI, not AI for MBSEEvery engineering company is asking which AI tool to bolt onto its modelling stack. I think that is the wrong question, and I wrote seventeen chapters on why. What is in the book, what is finished, and who it is for.