docs: best practices

[tim-sh]

These are somewhat opinionated, discussable rules that I nevertheless thought useful to improve quality.

[tim-sh]

OK, that should be it for this PR :)

[daogrady]

Can we have as many of them as possible expressed through lint rules?
While some, like "meaningful names", are likely impossible to detect automatically (AI?), for at least some there should be appropriate rules. For example, there appear to be plugins concerned with restricting mutability.
I am a strong proponent of clean code and consistent style, so I am strongly in favour of establishing a style guide. But as these best practices are not org-wide, I'd probably stumble over them again and again when having to switch context and making sure I adhere to them. So having The Machine(tm) slap my wrist would be nice.

[tim-sh]

I’m with you and I think that’s a good next issue. The present PR is concerned with documenting it first.