yosh

Want to build a tool to document papercuts. I think there's a lot of value to be had in documenting the small speedbumps you experience, at the time you experience them. Think the optimization path from "good" to "excellent" often lies in figuring out where the papercuts are.

Tool would be really simple. Run a command which then prompts a few questions about the topic, short description. Then it opens an editor window, with a filled out markdown file ready to have more details added to. Once done editing, the tool continues. Committing. Uploading.

I think I just described 20 lines of shell haha. But I think there's good value to be had here, which is the important part.

Oh. My. God. While writing this I just discovered %F for the `date` command. $ date +%F 2018-05-16 No more messing around with `%Y-%m-%d` which I *always* mess up.

Neat, okay - filed my first papercut: "Borrowing from a match statement isn't possible". Hope it's useful! https://github.com/yoshuawuyts/papercuts/blob/master/2018-05-16-rust.md …

Also here's the tool I wrote on the plane over https://github.com/yoshuawuyts/dotfiles/blob/master/bin/papercut …

Wrote down another one I ran into last week - Rust's `.unwrap_or()` methods: https://github.com/yoshuawuyts/papercuts/blob/master/2018-05-16-rust-or-else.md …