GitHub now provides a feature to discover when you've accidentally leaked company private keys: https://developer.github.com/partnerships/token-scanning/
Makes sense, but it's a shame it's needed. It's easy to screw up.
miniblog.
Related Posts
Today I learnt about clippy::clone_on_ref_ptr, which complains about t.clone() on a Rc<Thing>. You write Rc::clone(t) instead, so it's obvious it's a cheap clone.
It's a nice approach, because it makes the expensive clones more obvious.
Reviewing some of my earliest web projects: they have a mix of Postgres, MySQL and Mongo.
These days I just use sqlite for all my personal projects. It's really good at my scale and makes deploying very easier.
Are there any developer experience advantages for `x := 1` over `let x = 1`?
A `let` keyword probably improves parsing error behaviour, and makes declarations more visible.
:= is more concise though.