About
Hi, I’m Kemo. I write k13 to understand what changed before it bites.
I'm a full-stack developer. I write about Node.js backends, small infrastructure and tools that stay out of the way: what a release really changes, what breaks, and what to check before you ship.
How the articles are made
Short version: sources first, opinions second, and a checklist you can run at the end.
- 01
Every claim is linked
Release notes, docs and benchmarks are cited inline, next to the sentence that uses them, so you can check the source in one click.
- 02
Drafts are reviewed by me
Some drafts start with an AI assistant. Nothing is published until I’ve read it, run the code and corrected it.
- 03
Built on its own editor
k13 runs on k13 Pages, a block editor I’m building. Every article is one JSON document, rendered by the same blocks you’re reading.
Contact
Spotted a mistake, or want an article on something?
Corrections are fixed in the article itself, with an updated date. Article ideas from readers go on the list.