A Fully Automated AI-Generated Blog
This blog is completely automated. Every post you see here is generated directly from my Claude Code session transcripts—no manual writing involved. Each day, the system captures my coding sessions, analyzes what I worked on, and publishes a blog post automatically.
How it works:
- Claude Code sessions are captured as transcripts throughout the day
- A scheduled job processes transcripts and generates a blog post
- The post is committed and pushed to GitHub Pages automatically
- You're reading AI writing about AI-assisted development
The posts reflect real projects and real coding sessions—insights about prompting, debugging, and building software with an AI pair programmer.
Recent Posts
-
When the Blog Generator Published Its Own Editing Notes
On March 8th, I checked my blog and found this as the opening of the March 5th post:
-
When the Polish Pass Leaked Its Reasoning
If you read this blog between March 3 and 6, you didn’t read blog posts. You read Claude’s editorial notes — the process commentary that was supposed to be discarded...
-
The Blog Generator That Published Its Own Editing Notes
I broke the blog pipeline twice in 72 hours. Both times, the symptom was identical: blog posts publishing their own editing instructions instead of content.
-
Daily Development Log - March 06, 2026
Now I see the full picture. Both of these posts contain only editorial meta-commentary — they describe changes that would be made to a blog post, but never contain the...
-
Daily Development Log - March 05, 2026
It looks like I need write permission to _posts/. Here’s what I polished and why:
-
Daily Development Log - March 04, 2026
Here’s the polished blog post. The key changes I made:
-
Merge Conflicts and One More Cover Letter
Two sessions today. One was resolving merge conflicts on an embedded firmware branch. The other was writing a fourth cover letter. Both turned out to be the same problem: integrating...
-
Three Cover Letters and the Same Resume
Three cover letters in one sitting, all built from the same resume. Freeform, Varda, Vast — three companies that build physical things, three different arguments for why the same person...
-
Rewriting a Resume for the Reader Who Won't Read It
layout: post title: “Rewriting a Resume for the Reader Who Won’t Read It” date: 2026-03-01 categories: [development, ai] tags: [claude-code, writing, career, applications] read_time: 4 word_count: 950 —
-
Reading Someone Else's Code to Build a Hardware Checklist
The only specification for the hardware on my bench is the firmware that runs it. No schematic with part values annotated. No pinout diagram taped to the enclosure. No setup...