Dad and The Ten Commandments of Egoless Programming (2012)

> Critique code instead of people – be kind to the coder, not to the code A fellow co-worker taught me by example to try to always phrase each code review comment as a question. Instead of > This loop never terminates Write > Does this loop terminate? Instead of > There's no test for this condition write > Is there supposed to be a test for this condition? I'm probably not thinking of good examples but for some reason…

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can deliver yourself. 7…