Devops ninjas can envision and architect a solution that will not only solve the problem in test and production when it's released to the current user base. A true devops ninja can foresee a time when your company is bought and a sudden influx of new users are brought onboard.
5. You like sharing
Do you enjoy helping others? Personally, I love the feeling when someone comes up to me and is truly thankful for assistance I provided. It makes me feel good to know that I can share my experience with someone else. If you're going to be a devops ninja you must share in this mentality. No one's going to take your job. No one's going to "steal" your idea or your work. It's time to set all of that aside and think for the team rather than covering your own butt.
Devops is about sharing your successes and failures for others to learn from regardless of your ego. Egos have no place in a successful devops shop. If your team is truly practicing devops, your failures will be treated as learning opportunities and your successes will be awarded. If you truly share your work and receive the opposite responses, I'll go out on a limb and say, "It's not you; it's them."
You must be transparent and open in your day-to-day activities in order for your team to measure what works and what doesn't.
6. You can "let it go"
Devops is rooted in trust; trust of your team and of the business itself. Any member of a team practicing devops must be able to trust that others can do their jobs as well as or better than they can.
A true measure of trust would be demonstrated by working on a particular software feature that you envisioned, proposed, and built yourself, and when the time comes for you to work on another project, you hand your baby off to another developer. You must be able to let it go -- to trust that your feature won't be bastardized or taken into an extreme new direction. Even if it happens to do so, you must be able to live with it and understand that the users and business has mandated this new direction.
You must be able to depend on your team members, and if you feel you can't, you must approach them and have that awkward conversation. If they themselves are approachable (Talent No. 3), this should be easy.
7. "It's not my job" is not in your vocabulary
Developers with pagers?!? Sys admins who code?!? What's this world coming to anyway? Devops, that's what. "It's not my job" should be erased from your vocabulary completely. This isn't to say you're going to be able to assist everyone for every task -- quite the contrary. This is about either assisting, when you can, or pointing them to the right person who can.
Sign up for MIS Asia eNewsletters.