The Writing Build
How I use a machine to write more without sounding like a machine wrote it.
Everyone has a robot that writes now. So everything is starting to read the same. Same rhythm, same words, same fake polish. The edge used to be access. Now the edge is voice. This build exists to protect mine.
- A voice memo app. The whole build starts with me talking, not typing.
- One frontier model with one job: organize my words. It never writes new ones.
- A second model as the critic. It flags weak spots. It does not fix them.
- A ban list. Words and tells that never make it through, no exceptions.
- Talk first. I record while I walk. Messy and half formed, on purpose. If an idea can't survive being said out loud, it isn't an idea yet.
- Hand over the transcript with one instruction: organize this, keep my words. The model can move furniture. It cannot redecorate.
- Rewrite the whole thing myself, out loud. If a sentence wouldn't survive a kitchen table, it gets cut.
- Run the tell check. Em dashes come out, because nobody I know actually types those. Ban list words die on sight. Three perfectly balanced clauses in a row is a machine's rhythm, so I break it.
- Ship it small. Post, watch the replies, fold what worked back into the build.
Models drift. A prompt that behaved in March acts different by June. I keep the organize instruction short and boring, because boring prompts age better, and I retest it every time I switch models.
The model is a fast intern with no taste. Taste is the whole job. Outsource the typing all day. The moment you outsource the voice, you have nothing worth reading.
Everything here, sent straight to you.
New builds, scouting notes, the occasional strong opinion. It goes out when there's something worth sending, not because a calendar said so.
Found me on X, LinkedIn, or YouTube? This is home base.
That did not go through. Try again in a moment.
No spam. Leave whenever.