Wat started out as a simple wrapper around tldr and cht.sh. But they don’t provide good facilities for adding personalized documentation of my own that’s where wat comes in. There are a few excellent projects that provide succinct documentation for *nix commands: tldr and cht.sh are my favourites. The average man page is more like a lengthy novel than Cliff’s Notes it’s thorough+exhaustive documentation when I just want a quick reference. Unfortunately, man pages usually aren’t designed for this. So, like many people, I used to spend a lot of time digging through man pages when 1) I know what I want to accomplish 2) I can’t remember the exact CLI syntax to make it happen. It’s easy to remember the handful of commands+flags you use on a regular basis it’s much harder to remember the ones you only use a couple times a year. I spend a lot of my day in a terminal, and command line interfaces have notoriously poor discoverability.
I really love the analogy, and it’s inspired me to write about one of my own “home-cooked” tools: wat. It’s about highly personalized programs when you build something purely for yourself or a small audience, it’s more like home cooking than industrial production.
DOTBOT FISH CODE
Robin Sloan’s post about “home-cooked” code has been making the rounds, and for good reason.
0 kommentar(er)
