What Do You Do When Your Mind-Numbing IT Job Should Be Automated?
jfruh writes Not everyone has a job like Homer Simpson, who's been replaced at various times by a brick tied to a lever and a chicken named Queenie. But many IT workers have come up against mind-numbing, repetitive tasks that probably could be automated. So: what do you do about it? Well, the answer depends on how much power you have in an organization and how much your bosses respect your opinion.
QUIT
Learn how best to automate that task so you can start on other projects to automating other tasks.
New things are always on the horizon
I've ended up creating a few solutions where I think I'd rather spend three hours doing something creative than one hour doing it mindnumbingly dumb and repetitive. Often the maintenance of tweaking it eats up the savings.
Relevant XKCDs:
Automation
Is it worth the time?
Live today, because you never know what tomorrow brings
I always automate.
Then I get laid off because "I'm not doing anything."
People who don't automate, and get paid by the hour to do the same thing over and over again stay on.
Automate it and find something else to work on. At no place I've ever been has there been a shortage of work.
Only the lazy and incompetent fear automating themselves out of a job. If worst comes to worst, you'll end up maintaining all those scripts you created, fighting fires, and dealing with the "one off" situations that the scripts can't handle.
I do not fail; I succeed at finding out what does not work.
That is what documentation is for.
Not just user documentation, but also system documentation. Good commenting of the procedure can also help.
Without the documentation you can't pass on the procedure (or support).
Now, even without documentation, it becomes just your baby... Maybe it helps you do your job, but you better have SOME documentation so you will know what it does, and how to change it when you HAVE to change it in the future.
As so often XKCD says this much shorter:
http://xkcd.com/1319/