Refactoring English: Month 23
One-Line Summary
Should I stick with the book?New here?
Hi, I’m Michael. I’m a software developer and founder of small, indie tech businesses. I’m currently working on a book called Refactoring English: Effective Writing for Software Developers.
Every month, I publish a retrospective like this one to share how things are going with my book and my professional life overall.
Highlights ๐︎
- I’m debating between doubling down on my book or transitioning to another project.
- I’m experimenting with more lightweight retrospectives.
Goal grades ๐︎
At the start of each month, I declare what I’d like to accomplish. Here’s how I did against those goals:
Finish remaining typography improvements for the book. ๐︎
- Result: Finished most fixes.
- Grade: B
I made more improvements, but I’m not sure where to stop. I know there’s more to improve, but I also don’t think it’s the highest ROI thing to work on.
Publish one new blog post. ๐︎
- Result: Published The MustCreate Pattern for Go Tests
- Grade: A
This was a simple post, but I liked being able to share the tip. I’ve since found it useful in telling AI agents how to improve tests in my projects.
Refactoring English metrics ๐︎
| Metric | September 2026 | October 2026 | Change |
|---|---|---|---|
| Unique visitors | 43,864 | 43,968 | +104 (+0%) |
| Sales revenue (ebook) | $2,152.02 | $3,078.22 | +$926.20 (+43%) |
| Sales revenue (print) | $0.00 | $487.84 | +$487.84 (+inf%) |
| Total Revenue | $2,152.02 | $3,566.06 | +$1,414.04 (+66%) |
Visitors stayed almost flat relative to September, but a significantly higher proportion of readers bought in the “launch month.” $2.2k of October’s $3.6k was from launch week, which I wrote about last month.
It would be great if I could keep up $3.6k/month in sales, but it looks like I’d have to write a lot of blog posts and continue to get lucky with them gaining traction.
Should I keep focusing on the book? ๐︎
I officially launched my book in October, after almost two years of writing. On one hand, I feel like, “The book is done. Time to move on to something else.” On the other hand, I feel like, “The writing is done, and now it’s time to start marketing.”
The problem is that I don’t have any more great ideas for marketing the book. I can keep writing blog posts related to writing, but I worry those will just keep reaching the same people.
My best idea is to interview other authors. I did it once with Adam Gordon Bell. I enjoyed the conversation, but publishing the interview turned out to be a ton of work.
I think the big challenges I hit last time are one-time obstacles, so if I redid it, it would probably be 1/10th as difficult, especially because audio transcription has gotten even better in the last year. I also like interviewing because it matches my “succeed by championing others” strategy, which has been one of the most effective ways to find new readers for my book.
Experimenting with shorter retros ๐︎
I’ve been writing retrospectives every month since 2019 (minus two months I skipped to reset after selling TinyPilot). For the first few years, they felt obviously valuable and worth the investment, but I’m wondering if they still make sense.
One problem is that they take me about a week to write. Not like a full working week, but they occupy the portion of the day I dedicate to writing, so it’s a big chunk that I could be spending on other writing tasks.
I also end up frequently publishing my retros late. For half of every month, I feel like I’m running late and have a large, unfinished task on my plate, which is an unpleasant feeling.
I worry that my retros are burying what could be useful standalone posts. “Where do Refactoring English readers come from?” could have been a free-standing post on the book’s website. “AI-assisted coding is becoming a problem for me” also could have been its own post. Both might interest a higher number of readers than the people who follow my monthly updates.
Finally, I feel like I’m finding fewer valuable realizations from my retros than in the past. It used to feel like every month, the act of writing my retro caused me to notice some major opportunity or significant flaw in my strategy, but that’s happening less and less. Writing the retros just feels like a thing I’m doing out of habit.
The problem might also be what I focus on in retros. Writing this retrospective feels clarifying and helpful, and maybe it’s because I’m writing about an unsolved problem rather than reporting on what I did. The past few months, my retros have drifted to rear-facing rather than working out problems I’m struggling with.
For now, I’m experimenting with shorter, more lightweight retros.
Wrap up ๐︎
What got done? ๐︎
- Officially launched my book.
- Improved my AI agent sandbox by reflecting on “Why Are Coding Agents So Dumb?”
- I created a bot account so that the agent can create PRs to my repos but not merge them.
- I switched to VM-based agent environments so that the agent can do things like spawn browsers or inner VMs without running into environmental limitations.
- I added different agent profiles, so OpenCode v2 now auto-switches to a cheaper model on simple tasks.
- I added an “AFK” mode to OpenCode so it doesn’t stop to ask me a question in the middle of a task.
- I stopped using Claude Code and now only use it via OpenCode executing it from the command line to request a code review. I find cross-vendor code reviews really valuable.
Lessons learned ๐︎
- My retrospectives are probably more valuable when I focus on future strategy rather than reporting past events.
Goals for next month ๐︎
- Book an interview with another developer author.
- Publish a new blog post.
Read My Book

I wrote a book about simple techniques to help developers improve their writing.
My book will teach you how to:
- Create clear and pleasant software tutorials
- Attract readers and customers through blogging
- Write effective emails
- Minimize pain in writing design documents
Be the first to know when I post cool stuff
Subscribe to get my latest posts by email.