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.
-
-
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 …
Show this thread -
Also here's the tool I wrote on the plane over https://github.com/yoshuawuyts/dotfiles/blob/master/bin/papercut …
Show this thread -
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 …
Show this thread -
Also starting to doubt whether "papercuts" is the best term. Does it sound hostile? I don't mean for it to be hostile. Maybe "speedbumps" would be better? Or maybs "small-nuisances". The latter is a bit wordy though. Ghmmmm.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.