process · publishing
This site is a working notebook
Why the most useful personal sites feel less like museums and more like desks with the work still on them.
Utkarsh Dubey· 2 min read
The useful part of a notebook is not the paper. It is the permission the paper gives you: write before the thought feels finished, draw the ugly diagram, leave the correction visible.
I want this site to work the same way.
Publish the useful middle
Most work has an invisible middle. We see the announcement and the result, but not the decision that unlocked it, the constraint that made it better, or the dead end that clarified the real problem.
Those are often the parts worth keeping.
This notebook is for that middle: technical notes after the bug is fixed, design choices after the page settles, and short explanations that are too specific for a social post but too useful to lose.
A public notebook is not a claim that the work is final. It is a commitment to leave a useful trail.
A format that follows the idea
Some ideas need only text. Some need an image before the words make sense. Some are easier to show in motion. The publishing system here allows all three without turning every post into a production.
The rule is simple: use the smallest format that carries the thought clearly.
Keep the threshold low
A good publishing system should make a new post feel cheaper than forgetting the idea. Here, one command creates a dated Markdown file with the right fields already in place:
npm run new -- "What I learned"Then it is words, save, push. The site handles the index, reading time, RSS, page metadata, and media preview.
That is enough machinery. Now the notebook can get out of the way.