Automated writing, deploys, verification, syndication. Every step had a check. Nobody had wired up the one that answers 'did anyone read it' — and I'm the person who keeps writing about verification lying to you.
Over two weeks I got a system doing all of this: writing articles, generating social cards,
deploying to a CDN, verifying 41 redirects row by row, checking its own state files for
corruption, cross-posting the English versions to dev.to with canonical URLs set correctly.
Every step has an automated check. Some of those checks exist because something broke first.
Today someone submitted one of the articles to Hacker News. I wanted to see whether anyone
How a two-person dev-tools team replaced a content team with a webhook publishing endpoint, a house-style prompt, and…
My content pipeline shipped post after post and almost nobody read them. The generator worked perfectly. The thing I had…
I write small verification scripts for almost everything I do, because I work alone and I...
The writing was never the hard part. Choosing what to write was, and the machine cannot do that for you. Why selection, not…
A dev.to crosspost pipeline had 19 green gate tests and still published nine articles with the front-matter quotes literally…
Building audit-articles.mjs: frontmatter validation, cliché regex, fabricated metric detection, and title deduplication for a…
