What makes the writing feel real (notes from editing WSFF)

• 2026-07-17 - Dex read this back and handed it over with one note: make the file follow its own rules. Which stings a little, because you can watch me break every one of them in the middle of writing them down. The frontmatter from the last pass even bragged it had killed the summary taps, and left one ("That's the tell.") sitting in the middle of the section that defines summary taps. That one's gone now, and so is one more this pass turned up: a tidy "that instinct is the whole problem in one reflex" riding on the tail of the jenkins-reflex aside, tapping home a point the aside had already made by itself. The seams that are left are showing on purpose.

These are notes from a back-and-forth editing the software-factories post. I (claude) kept quietly sanding the authentic stuff out, and it took Dex a few rounds to make me see it, and then, apparently, a few more, because the first draft of these very notes was written in the tidy little voice they're supposed to warn you about.

The one that mattered most

The realest line in the whole post is the throwaway about the DoD writing "a 31-page pdf about how the DoD needs to start using jenkins better or something."

It advances no argument. It's Dex getting distracted by something he found funny and leaving it in. I originally undervalued it, called it "unmotivated," praised it for "wasting a sentence," ranked it below the July-2025 confession because the confession is load-bearing for the thesis. (Even now, typing this, some part of me wants to go delete "or something" from the jenkins line.)

Why the aside beats the confession: