One green square on the contribution graph this week. The autopost script ran on Sunday morning, dropped the previous week’s update into the content folder, pushed it to the site, and that was the entire commit history for seven days. If you were watching my GitHub, you saw nothing move.
I want to write honestly about what that looks like from the inside — because I think it says something useful to anyone considering hiring an independent developer.
What the autopost actually is
The Sunday autopost is a small script I wrote a while back. It takes the drafted weekly update, commits it into the MDX content directory with a consistent slug format, and pushes to the repo that deploys theapparchitect.com. The result is a commit that reads feat(blog): weekly autopost 2026-07-13 — automated, but not hollow. The post itself is written by hand. The script just removes the friction of a manual deploy step on a Sunday morning.
I built it because I noticed I was occasionally delaying posts by a day or two for no good reason beyond the small hassle of opening the terminal and running the deployment. That is the kind of friction that compounds quietly. The script costs nothing to run and removes a decision from Sunday morning. Worth it.
But the script being the only commit this week means nothing else shipped. No new features, no fixes, no refactors across any of the projects I maintain. That is the honest account.
What a quiet week actually means
I have written before about thinking weeks — time spent on architecture and planning that does not produce a green square. This was not quite that either. It was a week where life ran at a different pace. I am not going to dress that up.
What I will say is this: the autopost still ran. The post from last week — Sommelio going live on iOS and Android — is sitting on the site, indexed, readable. The public record did not go dark. That matters more than it might seem.
If you are a small business owner thinking about hiring an app developer, one of the harder things to evaluate before you sign anything is whether that person will still be there six months in. Will they keep you informed when things slow down? Will they be honest when a week was thin? The developer who disappears for two weeks without a word and reappears with “we made great progress” is a risk you cannot see coming until it is too late.
The build-in-public record is my answer to that question. Not every week is AutoBrew shipping three releases in 48 hours. Some weeks are one autopost and an honest paragraph. Both go on the record.
What is coming
There are two things I want to move next week. One is a deeper look at the DokuAI project — it has been on the roster since late June and I have not written anything substantive about what it actually does or where it is headed. The other is a small infrastructure change to how I handle MDX frontmatter validation at build time, which has been quietly annoying me for longer than it should have.
Neither is glamorous. Both are real.
If you want to see what working with an independent developer actually looks like — the sprint weeks and the quiet ones — the full picture is on /work. If you are ready to talk about a project, /contact is the place.