Slashdot Mirror
What Do You Do at Work?
mabhatter654 asks: "With all the talk of 'inefficent' and 'uncooperative' American workers, what do most Slashdot readers actually DO at work? Currently, I'm one of those 'IT' workers at a small manufacturer. Yes, I'm called the 'SysAdmin' but that changes monthly. I'm responsible for the companies network, AS/400, website, PC troubleshooting, phones, etc. But...I also get pushed into other things like ISO compliance, Quality issues, as well as babysitting the shop floor/nite QC on 'off' shifts on a regular basis. Of course, the 'SysAdmin' work suffers...when you spend more than half of your day on other tasks. But that does make me part of the inefficent IT problem that bosses like to talk so much about now days. I'm curious how many other Slashdot readers 'multitask' in non-IT rolls while officially still in that capacity. I'm looking for your 'title', company size, and both IT/non-IT tasks you perform. Also, Does 'multitasking' add more or less value to your position at the company. i.e. the IT tasks that don't ever happen versus helping management in another department? Oh yeah, how about those hours too! How much overtime do you put in and how much of that is due to the other work?"
You're asking slashdot, during the middle of the work day, what we do at work?
I can't say that I don't give a fuck. I've just run out of fuck to give.
My primary tasks include stomping out the various fires that crop up, and making sure our systems are up and available (in spite of the Children in Redmond).
I do a lot of one-on-one support, and fix anything that's broken. I get drafted to fill in the gaps whenever something comes up that we don't have enough resources for. (I just spent a day doing forms data entry, for example).
In my spare time (which varies from 40 to -20 hours/week), I've been spending quite a bit of time trying to plan out a migration to Linux. I'm free to pursue whatever projects I think will help the company. I also hope to eventually move our in-house database from Access 97 to MySql/Apache.
I read slashdot, k5, and a few other sites, to keep a watch out for the newest holes from the kiddies in Redmond. Yes, it counts as work, if I didn't do it, we'd have gotten crushed by things at least 3 times in the past 2 years.
--Mike--
"Yeah, I just stare at my desk, but it looks like Im working. I do that for probably another hour after lunch too.. I'd say in a given week I probably only do about fifteen minutes of real, actual, work."
and that 15 minutes is patching openssh
I maintain a database of half a billion dollars worth of excess aircraft parts using dBase IV for DOS. I also maintain the superfast network of Pentium 133s running Windows 98se.
Yes, I am quite happy when I get home to bask in the warm glow of my eMac running Mac OS X.
Interestingly, I'm having a discussion with my boss's boss who wants to know why we don't get more work done on projects. I've tracked our time and it comes out to about:
His response, predictably, was "Only 50% of time on projects? I can't believe you are only 50% efficient."
So, as a simple solution, we've started using RequestTracker It's a simple ticketing system, and everything in the "Interrupts" list goes into the system (otherwise we don't work on it.) And then each week I give a nice list of all the "other things" we worked on. It's been very useful defending my "efficiency."
...as long as it's not illegal or immoral and he's willing to pay my price. And I'm not trying to be funny.
In the last year, that has included IT security auditing, training on various office apps, database development, needs assessment, small network administration, technical writing, etc.
Title- owner. Company size - one. Being self-employed means plenty of non-IT tasks like bookkeeping and janitorial and marketing and purchasing. Hours? Depends. When business is good, I put in 80 hour weeks. When business is not so good, 40-60 hour weeks. But then I pretty much take off all of November and December and a couple of weeks in the summer.
I love my job. My boss is a bitch, but her profit-sharing plan is awesome -- I get 100% of the profits.
computerlady - a brand new Slash-daughter - alone, but no longer invisible, in the
I work in aerospace at a big US firm. We still have developers onshore: many of the US government contracts disallow foreign workers for security reasons.
Amazingly, most of my day is not spent working on software, but, on software process. There is all of the overhead involved in keeping our work instructions up to date and our software processes documented so that were are compliant with ISO 9000/1, and CMMI level 5. All of our specs and testing must be formally documented to keep up with DO-178B and contractual obligations.
Because the govt is the customer, there are bi-monthly presentations of our progress, with all the PowerPoint that that entails. The government has their own separate safety team that monitors our team, so a lot of time is spent interfacing with them.
As a consequence we are rather inefficient. To deal with that inefficiency we spend a lot of time in Six Sigma meetings tryings to come up with ways of automating work and creating reusable frameworks. These meetings are truly valuable (see, I'm not totally cynical) but they do take time and require their own documentation.
(The sad thing is that once all this process is up and running, the ISO/CMM documentation makes is so much easier for the company to treat coders like cogs in the machine or to move their jobs offsite. I am so thankful for the government security rules that make my job US citizen only. Whether or not we can keep our California site from moving to Nebraska or some such is another question...)
Where I've worked, IT wasn't regarded as inefficient but I think it's regarded as too expensive everywhere.
I'm used to management hating IT because it's a cost center. Here's what I wish I could tell management:
IT is hard.
You get what you pay for.
I'd like to see some of these managers try taking their car to a cheap mechanic.
IT requires acting almost compulsively, lots of obscure knowledge, and troubleshooting. Then there are the hours.
Troubleshooting is helped tremendously by natural ability, and is not easy to teach. The obscure knowledge requires being enough of a geek to keep up, and the more background you have in how stuff works, the better off you are. Compulsive behavior is a pain for most of us.
I know that the reason I got pulled onto other tasks was that they knew that I'd just Make It Work. I watched a former CIO pulling on cat5e with all his might when he was helping out on a cable run. If you pull on it too hard, it'll probably work, but you sure won't full bandwidth out of it. I often worked on nights and weekends to minimize impact on my office. Backups have to work and be tested. If you don't have backups, you might as well not have IT. I know places like that too, but what do you think of a software shop where nobody is specifically responsible for things like the FTP server, or there are no real backups?
Unfortunately, it's difficult to sell most of this on a resume. I guess that's where years of experience are suppposed to come in, but I know that in many cases that doesn't do it.
Where did you hear that American IT is inefficient? Is this some sort of specific story or rumor? Traditionally, American workers are very productive, and my experience in IT is similar. I know the network architect at one company where I worked saved them hundreds of thousands of dollars on their phone bills by redesigning their telephone system. IT has made a lot of other support staff unneccessary.
I like the mechanic analogy a lot. You can delay maintenance for a long time, and put up with little problems, but ultimately your car will require professional attention. Even for people who buy a new car every two years, maintenance is cheaper than doing none. With a few years experience, a mechanic at a dealership can make 80k.
Almost all of my coworkers in IT have worked their asses off too, even the mediocre ones.
Assembly is the reverse of disassembly.
I am a one-man IT department at a Los Angeles-based company with about 150 employees. I do pretty much everything that's even vaguely related to IT.
:-( ), and I'm coordinating the contractors doing this.
Recently, in only vaguely IT-related stuff, I have worked on the renewal of our phone system support contract, figuring out if an upgrade to our phone system is really necessary, and fighting with the phone system people over incredibly bad terms in a contract. (For example, when they upgrade the system from Windows NT 4 to Windows 2000, they deliver the upgraded system unpatched (!). I told them to patch it as part of their agreement and they said NO NO NO and I said YES YES YES and they finally bent, sort of[*]).
My main job is to develop and maintain my Linux-based CRM+web ordering system that I developed myself. I want to move it to MacOS X to make security administration easier, and that's been taking a lot of my time. But so has developing new software to communicate with a new distribution partner.
We're also replacing our Exchange server (required because of the Windows-based phone system
Finally, when someone's workstation fails or gets a virus or whatever, I have to help him, her or it out. I am incredibly irritated at all the Windows problems that come up, because they distract me from productive work. If I ran the company, nobody, and I mean nobody, would be using Windows. Ugh.
When I feel overstressed, I calm down by reading and writing on a whole bunch of sites, including Slashdot. Slashdot is also work-related because it alerts me to the worst security holes, new directions in computing I should be aware of, and the like.
Recently, I'd say fully 50% of my time has been spent on supervising contractors of various types, but that's extremely unusual. Most of the time I am working on projects on our CRM system and helping users with problems. But recently there has been a lot of supervision. For the most part, I consider it an interesting change of pace, especially since management is understanding about it delaying the other projects I'm supposed to do.
Except for now, when our Exchange server is being replaced next weekend, there's relatively little overtime except during emergencies. But then again, our business is a 8-3 business, more or less.
Hope that helps.
D
[*] (Yes, our phone system runs under Windows. It's called Interactive Intelligence, and I'll give you a free clue: Don't buy it. Don't argue that it's bad because it runs Windows, even though that, too, is true. Instead, argue that it's bad because maintenance is incredibly expensive, non-responsive and our VAR maintaining it is desperate for revenues. It also appears to require a complete hardware replacement every five years or so, which is not long for something costing as much as a house in a crummy area of Southern California. Because many of the support problems, including quasi-compulsory upgrades, are thanks to the software developer and not the VAR, I cannot recommend buying this software even if you find a better VAR than we did).
I'm supposed to read /.!
As a result, I am responsible for the following jobs:
What's my job title, you ask? "Analyst". I don't know what an analyst is or what I'm supposed to be analyzing, but that's apparently my job title. Apparently analysts don't get paid much, either.
I like the company and the people, but the job is stressful and my todo list is always overflowing. I've brought up the question of hiring more people on several occasions, but I always just get a nod and a, "Yeah, that would be nice."
Hours-wise, I try my best not to work over 40 a week, since I'm on salary and I value my own free time a lot more than I value the company (this might have something to do with how much the company values me, as reflected in my, ahem, paycheck). I pulled an all-nighter just once, and a few late nights to meet a deadline, but that's rare.
Let's see...
. I write delphi code, user interface design and database design for hospital project;
. I write php/javascript/html code, user interface design and database sesign for the web project;
. Server management is up to me;
. I do the network management as well;
. MS-DOS memory optimization (!!!) for the old software (e.g. new machines on client side). I do this because I'm the only person on the company that played games on MS-DOS back in 1994...
. Internal hardware support;
I'm doing some research in colege too... All of that consumes my brain to the last drop and I end up working 60+ hours/week.
It IS insane, but if you take off presure, I like doing all this stuff... don't YOU?
sorry if I can't write good...
\m/
I work as the solitary face of IT in a 50 person charity that runs courses to train people employment techniques (interviews, CVs, finding jobs etc.), and runs a UK Online centre (where people can go use the internet for free). This involves tech support across 4 different sites around the city.
I'd say things are spread out like this:
40% online centre IT: installing software, fixing machines, unjamming printers
20% OLC support: showing people how to use mice (literally), software, and logging people out when they forget.
20% Off-site support: you know, strolling out to one of the other sites, installing software, fixing problems (most of which I don't know about until I get there)
20% Other Stuff: Meetings, e-mail, phone calls, and keeping up with the world of IT.
Usually I do a 20 hour week, although this week I did a couple of all nighters removing some management software from the machines in the online centre, and replacing them with Win2k group policies.
Unchallenged Master of None. And I love it that way. I can always hire or outsource when we do need an unchallenged Master. I get to be the one and only IT person at a small subsidiary to a large financial company. I lay out the budget, make all the decisions on purchasing, outsourcing, business recovery, etc. I do a lot of paperwork for compliance purposes which I kind of hate. I spend the rest of my time training users, acting as help desk, evaluating new products and tech, and trying to keep up with all the security alerts I get from the parent corp. It has been a wonderful position. I love being the "CIO" of a tiny company.
That was the way it used to be. Recently the parent company has taken it on themselves to pull ALL IT functions under one roof. Somebody thought it would be a Great Idea to have one group of people be all things to all business units and subsidiaries. Consolidate to save costs. What a novel idea. It has truly been a nightmare. What used to take literally 5 minutes now takes 2 weeks and requires 800 signatures. It's the most inefficient set up I can imagine. My users are forced to call a centralized help desk that is staffed by inexpensive entry-level folks that have no idea what we do, what apps we have installed, what our business model is, what constitutes a risk, etc. These people are fine, but imagine your company's help desk if they got calls from other companies in different industries. When calls get escalated we get a visit from an upper level Corporate IT person who either
A: doesn't get it anywhere close to right because they've never seen half of the software we use to do business, have not been made aware of the security model, and have never been told what functionality we need.
OR B: They swallow their pride and ask me, so then get it right but resent me for being king of my little pond.
This is true for most departments - their business systems needs are very different from each other.
So where we used to be a fast nimble outfit that took every advantage of current and emerging technologies to gain efficiencies and stay on top of the competition, now we are a slow, backward, bureaucracy driven, lawyer ridden, hack shop that can't load an MS Office template without 2 forms, a signature, a phone call, a ticket number, and a 5 day turnaround time.. And that's JUST for an Office template to print out mailing labels. You don't want to hear about adding forms to our web site or patching a SQL server, or (OMG!) upgrading apps on a desktop PC!
It's a total nightmare. We aren't saving any money. We're much less efficient. The entire dept. is beyond pulling their hair out. The parent corp's Holier-than-thou attitude leaves us with no hope. And just about anything I could do to rectify the situation is a violation of corporate policy.
I went from loving my job to hating it to the point where I'm sick to my stomach in less than 3 months. And it has nothing to do with the efficiency of workers and everything to do with incompetent power-hungry management whose main concerns are buzzword compliance, covering their asses, and of course short term stock prices over long term profitability.
I'm not used to being a bitter person so I'm putting my energies toward getting the heck out of Dodge.
Operator, give me the number for 911!
Um, yea.. I check this site to make sure no one from work is browsing and posting. Yea, thats it.... And I have to do it often, too. You know, so nothing slips through the cracks.
What, me Tweet?
I run a Virtual Private Server hosting company. I'd say my most of my time was spent dealing with people.
That includes answering simple questions for potential customers. And every now and then answering 'hard' support questions which might have me googling around trying to find answers.
I spend a bit of time setting up new servers. That used to take hours per server. Now I've got a personal best of 30 minutes (and that included a fully featured kernel recompile).
Since my server setups are pretty standard and the management of them is pretty much scripted, the day to day management of a lot of servers isn't that much of a handful.
Other than the support and hardware side of things, its a bit of everything: Billing; updating the default software installs; working on the website; adding HOWTOs; finding cheaper/faster/better host servers and network connections; reading the wht forums; new customer setups; answering 4AM in the morning pages; ...
You sound like you need the serivces of Terry Tate, Office Linebacker...
"You kill the Joe, you make some Mo' Baby! Whoo whooooo!"
+++OK ATH