Nothing goes in the compost finished. It goes in raw, sits, gets turned over a few times, and only becomes useful once you stop expecting it to look like the thing it started as.

I used to treat a first draft as a rough version of the final thing — smaller, uglier, but recognizably the same shape. That's not what a first draft is. It's raw material, thrown in together without much plan, because the plan comes later, from the turning over.

What finally clicked for me was noticing that good compost doesn't smell like any of its ingredients anymore. In the same way, a piece of writing that's been turned over enough times stops smelling like your first idea. That's usually the sign it's close to done.

This matches my experience with code reviews, weirdly. A rough PR that gets turned over by three people ends up nothing like the first commit, and that's usually a good sign.

The line about not being able to trace which sentence came from which draft is going straight into my notes. That's exactly the feeling I'm chasing and never had words for.

Counterpoint: some things really do just need to be written clean the first time, or the turning-over never ends. Curious where you draw that line.

There's a slower bus that goes the same direction as the fast one. I started taking it deliberately, and it changed what I noticed about my own neighborhood.

The fast bus takes the main road. The slow one winds through three residential streets first, past a school, a barbershop, a mural I'd never seen despite living four blocks away for two years.

Speed is a kind of editing. The faster you move through a place, the more of it gets cut. Now I take the slow bus on days I don't need to. It adds eleven minutes and I know two shopkeepers by name because of it.

I do this with walking routes instead of driving the direct way home. Same principle, no bus required if you're close enough.

Eleven minutes a day adds up to a lot over a year though — how do you think about that tradeoff on days you actually are in a rush?

A running note, revised roughly monthly, of beliefs I've had to quietly retire. It's more useful than any list of things I've been right about.

I log the shape of the mistake, not the topic: "assumed the more expensive option was the better-made one," "thought I needed more time when I actually needed a clearer question."

Reading it back is humbling in a useful way, mostly because of the pattern across entries rather than any single one. I'm consistently wrong in a few particular directions, and knowing that is worth more than a hundred facts.

Starting one today. I think mine is going to be embarrassingly long in the "trusted a deadline that was never real" category.

Do you ever go back and cross things off if you're proven right again later, or is it strictly one-directional?

Constraint isn't the enemy of good cooking. The smallest kitchen I've worked in taught me more about sequencing a meal than any of the larger ones since.

One counter, one pan you could reasonably use at a time. Everything had to happen in order, because there was nowhere to put a third thing down. In a bigger kitchen that discipline evaporates fast.

I still cook like I'm in that small kitchen, even now that I'm not. The food doesn't come out faster, but there's less chaos in the middle of it.

Strongly agree, though I'll say a bigger kitchen is nice specifically for the days you're cooking for more than four people. Constraint has diminishing returns at scale.

Stopped weeding the back corner in June out of laziness, and it's now the part of the garden I actually like looking at. Curious if this was an accident worth repeating.

It's mostly volunteer plants at this point — whatever seeded itself. Denser and taller than anything I planned, and somehow it reads as more intentional than the beds I actually maintain.

Yes, and I've started calling it "meadowing" instead of "neglecting" which has done wonders for my guilt about it.

Careful with this near property lines though — my neighbor was not nearly as charmed by my wild corner as I was.