Pronounced "eight rules of devops"
Follow the community. They will mow down thousands of problems before you ever encounter them. Give back.
Be part of a team. Ensure that team is welcoming to other teams. We're here to help.
A good naming convention will often get you 90% of the way there for free. Be consistent.
Aggressively delete stale complexity at every opportunity. All code is tech debt.
If the developers can't ship code, you're bad at your job.
Always slide improvements and tech debt work alongside deliverables. DevOps doesn't generate revenue, the teams we serve do. Strike a balance.
Be affable. Presume you're the one doing it wrong. It gets more accomplished. Be the first to admit when you're wrong for the same reason.
The role is one of facilitating others. Engineers often know how to solve the problem in front of them but are obstructed by forces outside their control. Whatever that friction point is, look into it.