miniblog.

Go has an elegant approach to defining example functions, which are shown in docs as `main()` with the output: https://go.dev/blog/examples

Today I learnt that `cargo fix` won't fix code with compiler errors by default, but you can override this! $ cargo fix --broken-code --allow-dirty && cargo clippy --fix --allow-dirty This incantation does exactly what I wanted :)

If you created a large, successful OSS project, would you want to be BDFL or move on after a period? I see tradeoffs on both sides, although it's not a decision I've needed to make myself.