I was going through some old backup CDs and found one with a directory aptly named: My Writing. I had started writing a document on learning Unix in the middle of 2003 and never finished. Here is what I had so far:

Learning UNIX is a bit like mastering Shaolin Kempo Karate.

There are Shaolin masters that teach the art to their pupils. They guide the students by asking them questions – encouraging introspection. Each lesson builds on the one before it, much like children are taught to use building blocks to achieve basic motor skills before they’re asked to take a pencil in-hand to begin learning their alphabet. The notion that a concept must be learned gradually [insert some insightful time period here after research into the “building blocks” learning construct].

Unfortunately, we don’t have similar masters to teach UNIX to budding systems administrators. Forgive the corny reference, but there were quite a few times where I felt like a failing Obi-wan while trying to guide some new Jedi. They’re so eager to get into it and I felt pressured to teach them what’s interesting instead of starting with the basics. If you let the impatience win, you give them enough information to be dangerous without the wisdom to wield it responsibly.

One of the most valuable lessons I’ve learned as an administrator was taught to me by my very first mentor, Mike Plunkett. He told me: “always leave yourself an out.” That means backing up the data you’re going to be modifying, or testing and retesting your command line in a neutral environment before you bring it to production. Another good mantra is “pause and reflect.” Type the command, and then sit there and stare at it—literally. Contemplate your command’s effect on the universe and all of the electronic things that exist in it. Be prepared to execute your back-out plan. Expect it to fail so you don’t panic if it does.