Shipped the /log page, a microblog for short status updates. Lower friction than a full post, lets me share thoughts weekly instead of waiting until I have something "worth" writing about.
Short status updates about things I'm building, reading, or thinking about. Lower friction than a blog post.
Shipped the /log page, a microblog for short status updates. Lower friction than a full post, lets me share thoughts weekly instead of waiting until I have something "worth" writing about.
Been thinking a lot about the difference between understanding a system and being able to explain it. You can know exactly how something works and still fail to communicate it. Writing forces the gap to surface.
Static sites are underrated. No database, no server, just files. This whole site builds in under 10 seconds and costs nothing to host. Sometimes constraints are the feature.
Reading: A Philosophy of Software Design by John Ousterhout. The chapter on "deep modules" vs "shallow modules" reframed how I think about API surface area. Complexity should be buried, not distributed.
Spent the weekend debugging a race condition that only appeared in production. Turned out to be an optimistic UI update that didn't account for a retry. Lesson: optimistic updates need pessimistic rollback paths.
Keycloak BBL prep done. Explaining auth flows to non-security folks is genuinely hard the moment you say "JWT" eyes glaze over. Analogies help: a JWT is a signed boarding pass, not a key.
Every time I come back to Linux after a Windows machine I feel like I can breathe again. grep, awk, pipes... the whole composability philosophy just makes sense once it clicks.
Entries are stored in a JSON file. No CMS, no database there is just a text editor and a push.