This is a Just the Facts (JTF) post: generated by AI from my own raw material (voice memos, session notes) and a short outline I wrote, then checked by me. This post explains what that means.
I'm way behind on blogging. I've been trying to finish posting about our January trip to Hawaii, and it's November. So I'm trying an experiment: Just the Facts (JTF) posts. I supply the raw material and a short outline of the points I want to make. AI pulls the supporting details from that material, and I get a factual, bulleted post that I can actually finish.
The Problem
- It's November and I'm still posting about our January trip to Hawaii.
- My plan is to spend an hour a day on writing and the blog, but that hour keeps getting eaten. Something always seems to get in the way.
- Part of the problem is that I think real posts deserve depth and research, and that takes time I don't have right now.
The Obvious Choices
- Wait until I have free time. From what I can tell, that's never going to happen. Even when the current busy stretch ends, something else will probably come up.
- Have AI pick up the slack. At a minimum I'd lose my voice, and at worst I'd be publishing AI slop.
- Voice: AI writing can sound great, but it won't sound like me, and its word choices can make it generic. When I do use AI for writing, I spend a lot of time making sure the result sounds like me.
- Facts: AI fills in gaps, and it can present a set of facts in a way that isn't quite true.
The Middle Ground
- Combine three things:
- Verbose raw content: voice memos, notes AI generated during work sessions, code, and resources worth pointing to.
- A short, hand-written outline that lists the specific facts I want the post to cover.
- An AI prompt that asks for a fact-heavy post built around the outline, using only the raw content.
- The outline is the key piece. Summarizing my memos on their own wasn't enough. I tested this with a book review: four memos about one novel came to about 200 lines of notes, when I wanted about ten bullet points. Asking AI to merge them got it down to 69 lines, which was still long and repetitive and full of spoilers. When I added a short four-point outline, the same memos produced a 44-line review that said what I meant.
- The hope is a Just the Facts post: one that covers the key information I want to publish, gets the facts right, and doesn't read like AI slop.
What Makes This Work
- Raw content is easy to come by. I already have plenty, and making more is simple.
- Voice memos: I hit record on my phone and talk. FolderSync pushes the recording to S3, a script transcribes it, and Claude summarizes it into an org file.
- Coding sessions: I end the session with "write this session up as detailed notes."
- The Claude summaries of my memos are surprisingly good. They turn long, rambling recordings into something much more coherent than I remember saying.
- I take the key decisions away from the AI.
- Don't guess at facts: use the raw content.
- Don't guess at the key points: use the outline.
- Don't guess at the tone: keep it informational and bulleted.
- Each step is bite-sized. Recording the raw content, drafting the outline, generating the post, and editing it are all small jobs. The creative decisions should take minutes, not hours.
What May Make This Fail
- The posts could end up incoherent. Will they make good reading? Maybe not, which is why this is an experiment. Still, a post that's factual and gets the information across has value.
- Even with all the guidance, I'm still asking AI to produce something automatically, so it could go off the rails.
This Is About Me, but It's Also About You
- Publishing just feels good. Hitting the publish button is a free dopamine rush, and it feels like I'm getting something done. Not publishing feels just as icky.
- So yes, JTFs help me feel unstuck.
- But this isn't just about pushing out content.
- A main goal of my blog is to give back to the system that has helped me. Many of the software tools I use every day are open source, and a lot of the advice I follow comes from things people published on the web.
- The blog is my way of giving back. That might be a short
elispfunction that makes life in Emacs a little better, or some hard-won advice we learned visiting a water park. - JTFs are meant to be light on style but heavy on what matters: bits of wisdom other people can use.
Behind This Post
The outline I wrote
1. I have a problem posting - I've been trying to finish posting about our trip to Hawaii in Januaray, and it's November!
2. The obvious choices:
1. wait until I have free time - which by all indications will never happen
2. have AI pick up the slack, but if I do that, I risk at a minimum
losing my voice and at a maximum producing AI slop
3. Middle Ground: what if I combine three things:
1. Verbose raw content: memos, AI generated notes from sessions, code, notable resources
2. A short, hand written specific outline calling out the facts I'd like post
3. An AI prompt asking to write a facts-heavy, outlined focused 'post' from these items
4. The hope: I arrive at 'Just the Facts' post: a post that conveys
key information that I want to publish, that's factually
accurate and doesn't end up reading like AI slop
4. What makes this work:
1. I have both existing raw content, and new raw content is easy to
make. It's a simple as hitting record on my phone's voice app
and talking, or ending a coding session with 'write this session
up as detailed notes'
2. I'm taking key decisions away from the AI: don't guess at facts
(use the content), don't guess the key points of the post (use
the outline), don'rt geuss at the tone (keep it informational
and bulletted)
3. Each of these steps is designed to be bite sized: creating the
raw content, drafting the outline, generating the post and
editing. The creative decisions should take minutes, not hours
5. What may cause this experiment to fail:
1. The posts may end up being incoherent
2. As much as I'm guing the AI, I'm still asking it to create
something automatically, so it may go off the rails
6. This is about me, but it's also about you
1. Publishing literally feels good: hitting that publish button is
a free dopamine rush, and I feel like I'm accompishing
somemthing. Not publishing feels just as icky.
2. So yes, JTFs help me feel unstuck
3. But, this isn't just about pushing out content.
4. A primary goal of my blog is to give back to the system that's
helped me: many of the software tools I use every day are Open
Source, much advice I follow comes from content published on the
web.
5. The blog gives me a platform for doing this. Whether it's short
`elisp` function that makes life in emacs a little better, or
some hard one advice we learned while visitng a water park,
publishing let's me give back.
6. JTFs are intended to be light on style, but heavy on what
matters: bits of wisdom others can use.


























































