Link: When the "best tool for the job"... isn't.
When the "best tool for the job" isn't argues that what we might think is the best tool for the job isn't. (I'm not going to mangle its ideas by trying to summarize it more than that.)
This is an issue that I sometimes feel moderately acutely, since I use X Windows in preference to something like OS X, while the general view is that Apples are the machines for people who want both Unix and a decent user experience (and there's a certain population that questions the sanity and wisdom of Unix people who aren't interested in that migration).
(From the Voidspace Techie Blog, via Planet Python.)
How to irritate your successor (on Solaris)
How to to really irritate your successor sysadmin on a Solaris machine:
Set the machine's hostname not by changing
/etc/nodename, but by hand-editing a '
hostname foobar' into the
Of course, you won't want to keep the machine current on patches either; otherwise, your successor might take a much longer time to find this, and have a much less exciting day.
Important caution: for the safest results, insure that you are a long way away from your successor.
I must thank Solaris's
patchadd and associated infrastructure for
saving a copy of the old 'modified out from underneath it' init.d
scripts; without that I might never have figured out how this machine
had once worked.
(The modification was made right after the
network script normally
prints the hostname on the console, and it's relatively easy to find
where that message is generated, so I can contort my mind to see how a
sufficiently brute force sysadmin might set the hostname this way.)