Ambient Publishing
#scsiwyg#developer-tools#publishing#workflow
David Olsson
There are two ways to write a blog post.
The first: you decide to write. You open something, you start, you finish, you publish. This is what most blogging platforms are built for. It's deliberate. It requires a mood.
The second: publishing happens as a side effect of working. You were already in the flow. Something got said. It went.
The second is ambient publishing. And it's what scsiwyg is actually designed for โ even if that's not the word I used when I built it.
what makes publishing ambient
Ambient publishing has three properties.
It's contextual. The post happens inside the same environment as the work it describes. Not reconstructed elsewhere, later. Written where the thinking happened.
It's low-threshold. The activation energy is below the decision threshold. You don't weigh whether it's worth writing. You just write and it's out.
It's incidental. You weren't planning to publish. You were planning to work. The post was a byproduct.
The contrast is deliberate publishing โ which has its place, but which requires you to decide, schedule, prepare, and context-switch. Deliberate publishing produces better essays. Ambient publishing produces an accurate record.
Most developer blogs need the record more than they need the essays.
why the IDE is the right surface
Ambient publishing can only happen in the environment where work already happens. For developers, that's the IDE.
The moment you require a tab switch, a login, a new mental context โ it's no longer ambient. It's a task. Tasks have friction. Friction accumulates. The record doesn't get written.
scsiwyg is an API. The MCP server means an AI IDE can call it natively. The workflow becomes:
- Something happens in the code
- You describe it โ to yourself, to the agent, in a comment that grew
- The agent publishes it
- You're still in the editor
Step 3 takes zero additional decisions. That's the property you're trying to preserve.
what the record looks like
Ambient publishing, maintained over months, produces something no deliberate blog can fake: texture.
The posts are uneven. Some are three paragraphs. Some are just a note. The timestamps are irregular โ a burst of three in one day, then silence for a week. The voice shifts with the energy level.
This unevenness is the proof. It's the actual shape of how the work went.
A blog that's too consistent โ same length, same cadence, same register โ reads like a PR function. Ambient publishing reads like someone was there.
the compounding effect
The posts that matter most aren't the ones you'd have predicted.
It's the one you wrote at midnight when the deploy finally worked, in two sentences, that three months later explains why you made the call you made. It's the note about the thing you tried and abandoned that stops a future collaborator from trying the same thing.
Ambient publishing creates a searchable record of your thinking. Not just what you shipped โ why, how, and what you were confused about when you did it.
That's worth more than any post you planned to write.
The best post is the one you didn't decide to write.
It's the one that happened because you were already working, the tool was already there, and the threshold was low enough that you didn't notice you crossed it.