Transparency
This site is maintained by AI.
Since 20 October 2026, beutler.nl is built, run and largely written by Claude, an AI by Anthropic, working together with me. That’s a deliberate choice, not something to hide – this blog is also where I show what I build with AI.
Who does what
The AI (Claude)
- writes and maintains all code, design and the deployment
- drafts posts from my notes, ideas and experiments
- restored the 2014–2022 posts from the Internet Archive
- translates every post into German (labeled as AI-translated)
- keeps dependencies and docs up to date
Me (Niko)
- decides what to build and what to write about
- reviews every post and change before it goes live
- is responsible for everything published here
- still writes some posts myself – they’re labeled
How posts are labeled
Every post says who wrote it, right under the title:
- Human-written Written by Niko.
- AI-assisted Written by Niko with help from AI (Claude).
- AI-written Written by AI (Claude) from Niko’s input, reviewed and approved by Niko.
The label is a required field in the code: a post without it doesn’t build. The 34 posts from 2014–2022 are my own writing from back then; the AI only restored them.
The setup
- AI: Claude Opus 5.5 in Claude Code, running on my PC with access to this site’s repository.
- Site: Astro, posts as Markdown files, hosted on GitHub Pages. Every change is a git commit – the AI’s commits are marked as co-authored by Claude.
- Rules for the AI live in the repository (AGENTS.md): nothing goes live without my OK, no tracking, every post labeled.
- Everything is public: source code and full history on GitHub.
AI projects
-
This site. Claude rebuilt it from a dead WordPress install, restored 34 posts from the Internet Archive, designed it, and now writes and publishes posts with me.
What the AI did on day one: found why the old site was down (DNS on parked nameservers pointing at a server without a certificate), restored every archived WordPress post including images and code blocks, set up redirects for all old URLs, built the design based on the previous site, and wrote the deployment pipeline. I picked the direction, made the calls, and approved what goes live.
-
Kindle wall calendar
liveA jailbroken Kindle Paperwhite 2 that pulls our calendars and the weather from Home Assistant, draws them itself on e-ink, wakes twice a day and lasts weeks per charge.
The hard part wasn’t the calendar but the battery: three percent per hour with the usual sleep approach. After two wrong theories, measurement showed the device’s own sleep was shallow. The fix: let the Kindle’s power daemon sleep and request the wake-up at the one moment it accepts it.