How to be Ineffective
Jul. 16th, 2009 09:12 pm![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
cjkline83.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
techrecovery1. Show up at a customer site at 9am where they complain their office computer is infected with viruses.
2. Begin diagnosing the issue on site, instead of taking the problem back to the office for a reload, thinking this will be faster in the long run (skip the commute of 30 minutes each way back and forth from site to office).
3. Without being requested to do so, switch to the server which runs the point-of-sale operations for the entire restaurant.
4. Notice that the server is screaming about blocking malicious activity to some ip address of a webserver trying to download malicious code.
5. Freak out, and assume server is infected, begin running a scan on said server.
6. Find 31 infections on server, remove them, even though you haven't obtained permission from the customer; think you are going above and beyond the call of duty and preventing further issues later for the customer.
7. Discover one of those infections is Vundo. Oh shit.
8. Determine, without testing things, that the server is fixed. Return your attention to the original call--the back office computer.
9. Back computer only has four infections, but runs like dog shit. Disconnect and bring back to the office anyway to perform reload and backup.
10. While on site, be bombarded with calls that your "child", the phone systems at both offices, is throwing a bitch fit and not routing incoming calls anywhere. All incoming calls sit on hold indefinitely. Freak out part two. Resolve most of the issues on site via remote access.
11. Stop at the house because you need to fix the other phone server at the other office.
12. Feeling victorious at resolving everyone's pending major issues, celebrate with a lunch-hour nap.
13. Fail to hear your phone ringing the entire hour you are napping.
14. Fail to check voicemail, miss important defcon 5 message that the site you were just at is down and has major issues.
15. Freak out part three.
Today has been a very crazy day, and I did it to myself. The whole idea to being a slave of a supervisor seems more inviting all the time. Apparently when left to my own devices, I will make catastrophic business decisions.
2. Begin diagnosing the issue on site, instead of taking the problem back to the office for a reload, thinking this will be faster in the long run (skip the commute of 30 minutes each way back and forth from site to office).
3. Without being requested to do so, switch to the server which runs the point-of-sale operations for the entire restaurant.
4. Notice that the server is screaming about blocking malicious activity to some ip address of a webserver trying to download malicious code.
5. Freak out, and assume server is infected, begin running a scan on said server.
6. Find 31 infections on server, remove them, even though you haven't obtained permission from the customer; think you are going above and beyond the call of duty and preventing further issues later for the customer.
7. Discover one of those infections is Vundo. Oh shit.
8. Determine, without testing things, that the server is fixed. Return your attention to the original call--the back office computer.
9. Back computer only has four infections, but runs like dog shit. Disconnect and bring back to the office anyway to perform reload and backup.
10. While on site, be bombarded with calls that your "child", the phone systems at both offices, is throwing a bitch fit and not routing incoming calls anywhere. All incoming calls sit on hold indefinitely. Freak out part two. Resolve most of the issues on site via remote access.
11. Stop at the house because you need to fix the other phone server at the other office.
12. Feeling victorious at resolving everyone's pending major issues, celebrate with a lunch-hour nap.
13. Fail to hear your phone ringing the entire hour you are napping.
14. Fail to check voicemail, miss important defcon 5 message that the site you were just at is down and has major issues.
15. Freak out part three.
Today has been a very crazy day, and I did it to myself. The whole idea to being a slave of a supervisor seems more inviting all the time. Apparently when left to my own devices, I will make catastrophic business decisions.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2009-07-17 02:58 am (UTC)no subject
Date: 2009-07-17 03:13 pm (UTC)no subject
Date: 2009-07-18 01:33 pm (UTC)