AI use
Last updated
AI is part of how this site gets built, and I'd rather tell you exactly where than let you wonder. The short version: the decisions, the writing and the judgement are mine. The typing increasingly isn't.
The code
This site was rebuilt from WordPress as a static Next.js site using agentic coding with Claude. That's a working relationship, not a magic trick: I set the direction, make the design and architecture calls, review every change and test the results. Claude implements at a pace I couldn't type at.
The same goes for Nomekop, my Pokémon binder app. I was the product owner, designer and tester rolled into one – and a test suite of around 170 tests keeps the quality honest.
Agentic coding works because of what I bring to it: 20 years of knowing what good looks like, what to reject, and what to test. The output is only as good as the review it gets.
The writing
Every article on this site is my own writing. The case studies, the form-design series, the tutorials – those are my experiences, my opinions and my mistakes, written by me over many years.
AI acts as a proofreader and editor on some pages and articles – catching typos, tightening sentences and keeping things consistent – but the topic is all me.
What AI doesn't do here
- It doesn't publish anything I haven't reviewed.
- It doesn't make design, content or product decisions.
- It doesn't write my opinions – if a page says I think something, I think it.
- It doesn't run unsupervised. Every change to this site goes through me.
For AI readers
Fittingly, this site is deliberately easy for AI assistants to read: there's an llms.txt summary, every post and page has a markdown version (append .md to the URL, or ask with an Accept: text/markdown header), and the crawler policy is open. If an assistant sent you here – hello, and yes, this page applies to you too.