I don’t want this site to behave like a résumé with better typography.
I want it to feel like a place where somebody has been looking at things carefully and keeping the useful pieces.
That’s why I’m calling it a field guide.
A field guide doesn’t need to know everything. It records what was observed, what seemed important, and enough context to recognize the thing again later.
Working notes are allowed to be wrong
One of the reasons I like this framing is that a note can be provisional.
I can write down what I currently think about rendering, frameworks, performance, or developer tooling without pretending I’ve carved it into stone.
If the idea changes, the note changes.
That’s healthier than turning every thought into a declaration.
What belongs here
Mostly things about the web:
- architecture and rendering
- performance
- frameworks and their internals
- developer tooling
- experiments that teach me something
- small implementation details I know I’ll forget
And occasionally whatever else survives the walk back to the notebook.