Why this log exists
A low-friction place to dump what I learn while building — short notes by default, an occasional deep-dive when something deserves one.
I build across the stack every day — infra, backend, frontend, the odd shader — and most of what I learn evaporates by the next sprint. This log is the fix: a place to dump it the moment it lands, while it’s still fresh.
The rule: keep the bar low
Most portfolio blogs die because every post feels like it needs to be an essay. So the default here is a note — two or three sentences, maybe a snippet, maybe the gotcha that cost me an hour. If a topic earns more, it graduates to a deep-dive (like this one) with its own page. If it doesn’t, it stays a one-liner in the stream. No guilt, no backlog.
What you’ll find
til— a single thing I learned today.note— a slightly longer observation or opinion.deep— a proper write-up worth reading end to end.
That’s it. If you’re reading this on a portfolio visit — thanks for stopping by. The stream is below.