Slashdot Mirror
Do You Hate Being Called an "IT Guy?"
An anonymous reader writes "The phrase 'IT' is so overused, I'm not sure what it means any more. OK, maybe it's an ego thing, but I spent a lot of years in grad school, lots of years getting good at creating software, and lots of years getting good at creating technical products and I don't want the same label as the intern who fixes windoze. I'm looking at a tech management job at a content company that is trying to become a software company, and they refer to everything about software development, data center operations, and desktop support as 'IT.' I'd like to tell the CEO before I take the job that we have to stop referring to all these people as 'IT people' or I'm not going to be able to attract and retain the top-tier talent that is required. Am I just being petty? Should I just forget it? Change it slowly over time? These folks are really developing products, but we don't normally call software creators 'product developers.' Just call them the 'Tech Department' or the 'Engineering Deptartment?'"
When I graduated there was the programmer, technical designer, conceptual designer and analyst ladder to climb. And I tried it.
The you realize the tunnel view you get when following such a path. And after a couple of years of having tried to adopt a fancy name -senior consultant, senior anything- I resolved to name myself that what defines me. If people ask I'll tell them I'm a programmer. Doing well for years with a lovely family, a very good income and a sports car that turns heads. But still a programmer.
I can develop products -which is much more than coding-, I can look through the organization and suggest improvements and I can tell anyone paying me he's brilliant. Still I'm a programmer.
Mainstream will never be able to keep cracks charlatans so don't set your hopes too high on job titles.
Consider job titles at Google. Naming Vint Cerf an Internet Evangelist is a way of telling the world that job titles don't really matter and that the substance matters way more.
I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
It's just not very descript, the connotations that the term 'IT' has attached are different to those of 'programmer', at least to myself, and I've no reason to believe I'm unique with that. IT in my experiences will tend to be more office/user facing; easing other peoples use of other peoples products, dealing with word processing, spreadsheets, all that kind of stuff. Programmers create the stuff that the people in IT use.
Personally I find it easy to escape the label of 'IT' by not having a clue how to use Excel or Word leaving me very much being not the person to ask :-) System architecture, coding problems, no sweat, that stuff interests me, so that's the stuff I'm interested in being associated with. I don't look down on people who fix the office printers or get peoples mail clients working with their AV or whatever... I don't look down on teachers, but it doesn't mean I wanna be one or believe that calling me one is an accurate description.
The revolution will not be televised... but it will have a page on Wikipedia
I can't see why this would matter.
I can. Where I work (as in most places I imagine), the IT department handles the network and helpdesk. IT also includes database administrators. While the database admins can write some really good SQL, they don't know jack about networks or computer maintenance. This is all fine and good. However, management doesn't know jack about IT. So we end up with a bunch of database administrators trying to run a network and maintain computers. And management wonders why everything is falling apart all of the time.
Keeping the titles separate might help management make the distinction between the database guys and network engineers.
Request a Linux Shockwave player here: http://www.macromedia.com/support/email/wishform/
That's THE title at Bell Labs. If it's good enough for Dennis it's good enough for me.
Would you call someone who designs aircraft engines a mechanic? Would you call someone who designs central heating boilers a plumber? Would you call someone who runs a team working on ALU design at Intel an electrician?
My point is that nowadays IT is actually a trade, and mostly attracts the sort of people who in the past would have become plumbers, electricians and mechanics. Which is not to knock them, because these are essential and valuable trades, but basically they implement what other people have designed and specified. Programmers who are not just coders, systems designers, user interface designers - these are creative professions.
In the UK we have a terrible tradition of confusing professionals with tradesmen, caused by our emphasis on "administrative" skills. We've just had the Government dismiss their principal expert on drugs because he dared to disagree with the irrational "omg smelling cannabis kills you I need a stiff drink or five before I can go back to work" culture of the Government and the Civil Service. In a properly organised world we would sack the Government for lying to us, but in the mind of the Govt., Prof. Nutt's status is about that of a plumber. The point is that you go to tradesmen for advice on implementation of what you want to do, but you go to professionals to tell you what to do in the first place. You somehow need to get back to that position (I say you. I hope to retire in 5-6 years; then it will be someone else's problem. For now, I am quite happy being a software architect, because that is actually what I do.
From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
From what I've understood companies in the US are extremely tightfisted about giving information about employees, so you'd better take what little you get. If you were a DBA but all your resume says is "IT department" and that's all they'll confirm then you have an uphill battle just to convince them that you were in fact a DBA, and not the guy replacing broken keyboards and fixing paper jams who is now desperately seeking a new job.
Of course there's such a thing as title inflation so too excessive a title will set off bullshit detectors, but there's no reason to sell yourself short either. I'm hardly a career ladder climber, but I would react negatively to a job title that would sell me short with my next employer. While it's not as bad here as in the US, the resumes do get screen by recruiting companies and HR and not having the title could lose me interviews before I even got to talk about what I've been doing.
Live today, because you never know what tomorrow brings
I don't look down on people who fix the office printers or get peoples mail clients working with their AV or whatever... I don't look down on teachers, but it doesn't mean I wanna be one or believe that calling me one is an accurate description.
I once worked at a university (doing "IT" for the engineering school) and during one of the staff meetings, the management suggested that they could save money by having the computer science professors take over all the IT tasks in the school.
Fortunately one of CS profs quickly suggested that the EE professors could fix wiring and changing light bulbs and the Civil Engineering profs could clean bathrooms and unplug toilets. The idea died almost quicker than it was born. But it belies the point of this article. Most people have no idea what "IT" even means and assume that if you can do one thing with a computer then you are automatically able to do all things.
LOL An IT-Guy.. Ah well I have been at this since what.. 97 or so? Worked out in the field with telco guys, programmed routers, firewalls, linux boxes, fixed windows... data recovery.. so I am used to the guy thing. it IS a male dominated field.. so I accept it and go with the flow. Specially gaming ;)
And, I prefer the intelligent geek IT guy myself ;)