Quote:
Originally Posted by
gnatty8 
You realize this works out to an average of 14 hour days, 7 days a week, for the entire month right? That sounds pretty excessive. I don't think i-bankers even pull those hours.
It was excessive, but necessary. It's easy to hit those numbers when you stay for 30 hours straight a couple times a month, and I did work 7 days a week. :P This all happened soon after I had taken the job and before I had a chance to orient myself with all the systems. We had a couple major hardware failures and a malicious "hacker" (actually an insider with access that wanted my job) that deleted data within a 2 week period, so I just put in a ton of hours to a) put out fires b) plug the security leaks and c) get oriented quickly so that we could address all the other issues of poorly maintained systems. The previous guy didn't have appropriate security in place and the hardware hadn't been updated since the company was formed, so it had been building for years. It was pretty much a nightmare scenario. I made them give me a real budget and we have all new hardware and appropriate monitoring of all the systems now. We finished all the upgrades at the end of 2008. Plus, I have better help now (people i've had time to train myself). For most of the past year i've rarely worked more than 60hrs/wk and it's most often closer to 40. All of my big projects are done now so i'm just training my replacement, documenting code, etc. I'm the most relaxed I've ever been and the new guy will have a very easy time now that all of the big changes has been taken care of.