Immutable documentation at Etsy: https://codeascraft.com/2018/10/10/etsys-experiment-with-immutable-documentation/
Basically a list of notes on a topic, collaboratively written on Slack. Notes aren't edited, you just append new ones.
Could work very well, depending on your team's dynamic. Super low friction, and similar to fsbot.
miniblog.
Related Posts
I'm playing with Zeal/Dash so I can view stdlib docs offline.
(I've been coding on public transport recently, without a reliable data connection.)
Anyone have tips for making the most of this setup? AFAICT docsets are basically HTML underneath.
It took me way too long to realise that Arc<Mutex<T>> is basically a way to create multiple &mut T references (with runtime constraints).
This means that you can use plain &T and &mut T in the vast majority of your code. Most code doesn't need to care there's a mutex.
RISC-V seems like a great example of "commoditise your complements". If you're getting value higher in the hardware or software stack, a royalty-free ISA is valuable.
Creating an ISA is a ton of work. Once it's basically viable, it creates interesting opportunities.