I took this idea from Charles over at Razored Zen. I talk alot about my school work, typically because I'm blogging when I should be working on that sort of stuff, but I don't talk too much about what I do for a living. My day job is as a Director of IT for a smallish web company that produces a web application that allows larger companies to manage their Cisco devices. We also run a couple other smaller web apps.
That is me working on a day that I worked from home. I probably do that about twice a month, but I could do it once a week if I wanted. Usually I perfer to go into the office. Today a client called to talk to me about a functionality push that I had done the night before on my cell phone before I'd even gotten into the office so my day started at 7:45am rather than the normal 8am. There were a couple tiny issues with the push (that I had done around midnight the night before), but mostly he was happy. It was very good because the functionality was a bit late and had been buggy. It had been a bit of a test that my boss wanted to give a guy on my team--and the test did not go well. I had to speak very harshly to the guy about it and my boss knew about the issues from the client...bad situation. So I texted the guy who was working on the project so he could get some positive feedback. Once I got into the office I confirmed the times for the people interviewing on Friday.
Then I proceeded to work on code for a couple hours, but paused for a conference call to test some other functionality for a trouble ticket system for Hilton. I've been working on this for about eight months. The problem is that our system has to communicate with these other two systems and getting everyone together was a problem, but on this call everyone was happy...but then we had to talk about who had to cut the final red tape. After the call my boss came to ask me what had happened (even though he was on the call he didn't understand what was going on because it was very technical) so I gave him a debreifing. Then I had to explain a new task for one of my guys followed by helping another figure out how to do something. Then an email came that the system that we had just tested was offically going live at Friday midnight. Yey!
I got an email from a client who couldn't access a page. I determined it was because a document had only two letters in its name and the system was confused. Usually clients contact their account rep, but really important ones contact me directly. Typically I fix the issue, although sometimes I give it to one of the guys in my team. I guess I try to do the things that no one wants to do since I could dole it out as the boss. I try to get my hands the dirtiest.
Then I had another conference call about a product that we are thinking about purchasing. I had heard of an alternitive product the day before so after the call I found the other product and played around with it. I wrote up a document to my boss and the client as to which I liked better.
Our site was slow so I had to debug the issue. It stopped being slow so I just shurgged and called it a day. Although, I had to work on an issue with an import not working starting at 8 to insuring that I could mess with the system and it wouldn't affect users.
Today was fairly representive of my days. As you can see, I spend much of my time talking with people. I think that many people view software developers as code monkeys devoid from the business. Of course since I am in managmenet I spend more time with the business than a lower level person might, but since we are making products to be used by people, it is actually very social and highly team based. I do have to work late alot since sometimes I need to do things to the system during hours that won't affect our users. I usually joke that I am the last line of defence between us and the computers :)
Wednesday, April 22, 2009
at 8:12 PM