Great topic, and great start. Another anti-pattern I see is: "Do not file PRs on code that you hasn't been reviewed for accessibility to a human".
At first glance, this could seem to be redundant (downstream) of the suggested anti-pattern. But reviewing code doesn't necessarily mean reading all of it. A reviewer might want to unpack a function you already know well, because you specified it and saw it work (but never read).
Comments
Great topic, and great start. Another anti-pattern I see is: "Do not file PRs on code that you hasn't been reviewed for accessibility to a human".
At first glance, this could seem to be redundant (downstream) of the suggested anti-pattern. But reviewing code doesn't necessarily mean reading all of it. A reviewer might want to unpack a function you already know well, because you specified it and saw it work (but never read).