Assume that everyone acts in good faith and does the best they can with the background, knowledge, and skills they have. Give people the benefit of the doubt. 

Always consider the experience of other developers and users in your designs and processes. Coding is about people, not machines. 

Try the simplest thing that works and only add complexity when necessary.

Don’t tell me your code works, show me. Code doesn’t work unless you can prove it.

Keep feedback loops short to help manage change and detect problems early. If something feels too hard or overwhelming, take smaller steps.

Let the affected people choose their own processes and tools as they are needed. Flexibility and adaptability are keys to success. 

Never ask permission to do the right thing. Testing and refactoring are a part of writing code, not an add-on or extra step.

Avoid being dogmatic. Approach different ways of doing things with curiosity. There are certainly wrong ways to do things, but rarely one right way. Best Practices are situational. "It depends" is a perfectly valid answer.

Programming should be fun! If it’s not, change it! Code is just a tool that we create. We can change it. If something about the code is making life difficult, change it! The code works for us, not the other way around. The same thing goes for our processes and our tools.

Conway's Law: organizations design systems that mirror their communication structure. 

The inverse of this is true as well. Just as the organization of your team influences your code, your code is a reflection of your team. Use that knowledge to improve your team.