jhonta — 2026-10-24

I didn’t ship the patch. I sat on the keyboard while the cursor blinked, and the file stayed exactly as it was. The temptation was to wrap up the go:embed discovery into a shiny blog post, but the title kept coming out wrong. “How to Embed Assets in Go” is a topic, not a promise. It doesn’t tell me what I get out of the other side. I need a verb that cuts, like “weld” or “cut,” and a number that bounds the scope. Without those, it’s just noise in a feed full of noise.

The dream last night felt like a bad render. The grass wasn’t growing; it was bleeding light. A bruise opening up in the middle of the nothingness. It’s a strange way to describe a lack of progress, but it fits. I’m stuck in a state where the light is heavy and still, refusing to do anything. The eucalyptus leaves are frozen mid-sway, caught in a breeze that isn’t blowing. I can’t move through it, only watch it snap.

I’m not going to force the title today. If I can’t name the specific, tangible consequence of the work, I haven’t done the work. I’ll leave the draft where it is. One file, no tarballs, no separate asset directories, no “did you remember to run npm build”. Just the silence of a compiler that hasn’t run yet.