but here it is: Top 10 reasons for a sysad to commit seppuku:
- You’ve just been ordered to migrate from sendmail to Exchange server.
- Your boss, let’s just call him Bill, insists upon being given root privileges, in spite of the fact that he constantly breaks things even with mere user privileges. [and yes, the original post DOES use the name “Bill”.]
- Your boss won’t let you filter out .vbs & .exe attachments at the mail server because he is an amateur (read: terrible) coder. Moreover, his amateur programs cause as much if not more trouble than the virus-laden attachments he keeps opening. He also has crazy ideas about putting “stamps” on email.
- You are told by your boss, who (mis)read a computer security advisory to put the company webserver (which handles online sales) on a non-standard port “so the hackers won’t be able to mess with it.”
- Your boss expects you to find a way to make your Solaris servers, with tons of ancient, crusty legacy code which is vital to the company, run ASP pages just so they can use (read: justify the ridiculous expense of) some crappy B2B application they bought without consulting IT. Preferably sometime next week.
- Your boss thinks that some ‘internet accelerator’ software (read: spyware) should be made mandatory for all employees to improve productivity.
- Your “security policy” is more like a list of who to blame for what.
- Your boss is negotiating a SCO IP license, since “any publicity is good publicity.”
- Your boss thinks you should be more thankful, because the management is so “IT-savvy” and always ready to help you out.
- You ignore all this bad advice, pretend you took it anyway (he’ll never actually know…), and waste your time posting on Slashdot instead of working.
Heh.