Zsh Functions I Actually Use Every Day
I've deleted dozens of clever shell functions over the years. These are the small, boring ones that actually stuck around.
Ieum
I've deleted dozens of clever shell functions over the years. These are the small, boring ones that actually stuck around.
Adding an index and hoping is not a strategy. Here's how I actually diagnose slow queries before I touch the schema.
Ship It, part three: the build was reproducible and the release script was solid. All that was left was an actual server to put it on.
I've deleted dozens of clever shell functions over the years. These are the small, boring ones that actually stuck around.
Adding an index and hoping is not a strategy. Here's how I actually diagnose slow queries before I touch the schema.
Ship It, part three: the build was reproducible and the release script was solid. All that was left was an actual server to put it on.
Optimistic UI feels great until two requests race each other. Here's a small hook I use to keep it predictable.
Ship It, part two: I had a release checklist in a text file that I re-read every time and still managed to skip a step eventually. So I stopped trusting myself.
My first five sourdough starters all quietly died. Here's exactly what was different about the sixth one, step by step.
Most of the token savings didn't come from clever wording. They came from structural changes to what I was sending on every single call.
Most "productivity setup" advice is aesthetic. These are the handful of changes that measurably cut down how often I got pulled out of focus.
Ship It, part one: before automating anything else, I had to fix the fact that my build only worked reliably on my own laptop.
Closing the reading log with a research paper, not a book — and the study habit I've actually changed because of it.