Just sayin'....

[mangosteen]

Coffee: Because falling asleep with your hands poised over the keyboard at a root prompt is Bad.

Observation: Red-eye flights continue to suck, but they allow for a full three days on the left coast, while only burning one vacation day. I can still do this and be vaguely productive the next day. For this, I am grateful.

Comments

[jbsegal.livejournal.com]

Mike Grubb used to tell about doing installs in the early days of the Akamai network where he'd wake up at his KB (at 3-4-5 am) and go "What did I just do?"

The entire effort of the install tools development was to A) Have them end earlier and B) keep people from having to wonder what they just typed. :)

[kalimar.livejournal.com]

A nice place that I get coffee from is Community Coffee. Yes you can order online. Yes they have a good selection. Yes the coffee is good.

[exponentialdk.livejournal.com]

That's why I often start a sensitive command with a punctuation character that will cause a syntax error. Then when I'm convinced I've entered the right command, I remove the prepended character and execute it.

I've lost count of the times I've woken up with waffle-face (keyboard imprint).

[cos]

I like to use "echo". It's a big part of the practice I like to call "defensive sysadmin'ing" :) The advantage of echo is that it'll often tell you more about what you're about to do than just looking at your command line again after a syntax error. For example, if you have a glob, you'll see it expanded. If you're about to run a find, put the echo after the find and see all the commands you would have run, etc.

[exponentialdk.livejournal.com]

Good point, thank you.

I can't remember the last time someone taught me anything about defensive sysadmin'ing. It may well have been 15 years.