Laziness is a great quality when automating repetitive tasks. Laziness flies in the face of learning new technologies and getting new work done. Somewhere between Jr. SysAdmin and Systems Architect, laziness is no longer an advantage. Let’s look at five laws aspiring DevOps folks should follow to be successful.
Forget ‘I don’t know’
- Banish the phrase, “I don’t know”
- Smarter ways to say it
- Treat every task as an opportunity to learn.
- Make an effort to not ask your peers how something works without reading its documentation first.
- Time is life’s most precious resource.
- In the absence of documentation, read the code.
Search before asking
- On the rare instance in which you must consult your manager, make sure you have at least searched for possible answers.
- Solving new problems requires searching for new answers.
- “Don’t bring me problems. Present solutions to me.”
Anything is possible. Never say never. Trust but verify.
- The beautiful thing about working in DevOps is that physics is the only limit in your environment.
- When it comes to complex, distributed systems—or even simple scripts—you should never assume anything.
- Trust your gut.
Acknowledge technical debt
- Technical debt is the result of decisions that made sense at the time someone made them.
- If you are on a DevOps team, you are either helping to eliminate technical debt or you are pushing it to production.
- Technical Debt, much like monetary debt, is something that can be managed effectively. People have debt that is good (a mortgage for example).