And B must be for Body of course

A once in a lifetime experience!

I generally agree and like this strategy, but to add to the other comment about catching reimplemented code, there’s just some code quality reviewing that cannot be done by automating tooling right now.

Some scenarios come to mind:

• code is written in a brittle fashion, especially with external data, where it’s difficult to unit test every type of input; generally you might catch improper assumptions about the data in the code
• code reimplements a more battle tested functionality, or uses a library no longer maintained or is possibly unreliable
• code that the test coverage unintentionally misses due to code being located outside of the test path
• poor abstractions, shallow interfaces

It’s hard to catch these without understanding context, so I agree a code review meets are helpful and establishing domain owners. But I think you still need PR reviews to document these potential problems

I generally agree. However, for the MDN Web docs icon, I’m not sure I’ll ever acclimate to that one, even with how often I see it. so bad. Love MDN still though

I second the recommendation of giving Linux Mint a shot. I didn’t use XP extensively but Mint is low hassle and gets out of your way.

I’m not sure it has quite the same feel, but closest I can think of that is also approachable coming from Windows. Obviously a lot of other distros also satisfy the “built by engineers” vibe.