Slashdot Mirror


Which IT Careers Are Hot and Which are Not?

necromante asks: "I've been working on different IT positions through my career: support; some networking; DBA; web development; project management; even working on the client side for a little while. However, I don't feel like I am really a specialist on any of those subjects and I feel I need to focus on a particular field. So, I decided to ask for some feedback before making my decision. I understand that this depends everyones tastes, likes and dislikes. However, I would like to have a better idea of which are the available options, and I hope the results of this discussion can benefit other readers. Is there any IT career that I should consider more than the others? Which are the emerging fields? Is there any industry I should focus on in particular? Which careers on IT are actually more in demand and which ones not? Is it a better path to focus on moving into management?"

37 of 284 comments (clear)

  1. Good techies don't necessarily make good managers by rf0 · · Score: 5, Insightful

    I've worked for a number of people and myself one thing that seems to come up is that good techies don't always make good managers. So don't assume that managment is right for you (or that you would even enjoy it).

  2. Domain Knowledge by Anonymous Coward · · Score: 4, Insightful

    A lot of demand has to do with your demand knowledge. I don't know if you could say with a broad stroke that devs are in more demand than DBAs or whatever. If you have financial experience for instance, demand is pretty strong across the board. You need to consider the industry you want to work in as much as the role you want to play.

  3. emerging fields: by farker+haiku · · Score: 5, Funny

    Which careers on IT are actually more in demand and which ones not?

    Editor who doesn't rely on spell check.

    --
    Your sig(k) has been stolen. There is a puff of smoke!
  4. Being a manager... by Hoplite3 · · Score: 5, Insightful

    When you were young, did you ever play video games with an older sibling where they played and you watched? Your brother would insist that you were "a team" and wouldn't let you play. Being a manager is like being the little brother, but you do get to fire the other guy if he dies five times in a row on level 8-2.

    Seriously, if you like something, why stop doing it and start just watching people do it?

    Oh, money.

    --
    Use the Firehose to mod down Second Life stories!
    1. Re:Being a manager... by Anonymous Coward · · Score: 3, Interesting

      One other reason to get into management though is the lack of time to learn the latest programming language du jour.

      Once you get older and start a family the time that you have outside of work to sit down and learn D++ or Python.Net or whatever gets a lot harder to come by.

      If you have the opportunity to learn on the job that's great. But it's not always the case.

      Even if it's what you love to do it's still gets harder to find time to do. So moving into management seems like a reasonable step.

      Although I'm putting it off as long as possible myself. ;) But I see it coming some day.

  5. The Fileds You Love by eldavojohn · · Score: 4, Insightful

    ... and I feel I need to focus on a particular field.
    Why?

    Personally, I value breadth over depth. And I'm going to propose a reason why everyone should also: in the world of computer science, at any minute a once vital skill could be obsolete. Granted, it doesn't happen often (as we still need workers to maintain cobol & fortran code) but, instead of spending my free time hunched over Enterprise Java Bean projects learning their delicate intricacies, I find myself learning about Ruby, Spring, Hibernate, etc. Now, I might not be an expert in any of these fields but I may be glad when their time comes. All good things come to an end--and if EJBs were to be retired, I'd certainly like to know my way around these other frameworks & tools. I think the same can be said about fields of computer science. Be wary of the web developer that doesn't know the first thing about networks & server/client communication--that's often a pitfall for security.

    So if you want my honest opinion about which "are hot or not," I think they're all pretty damn hot and I bleieve you can find money in any job where you make yourself usefull & valuable to a decent business. I find them all attractive because I enjoy setting up networks in my house and playing network administrater even though I don't do it at my job. I love networking Linux, Windows, FreeBSD, Solaris, etc. and I like toying around with different databases. I love to start new projects that rarely go anywhere but leave me with more understanding of how technologies or products work. I'm not a "trained expert" at any of them though, most importantly, I feel that I could easily become one if a situation deemed it necessary. If you don't enjoy doing some of these things--DON'T DO THEM. Who cares if they pay alot or are "hot"? I'd rather die happy & poor than rich & sad.

    Is there any IT career that I should consider more than the others?
    Of course there is, it's the career you enjoy the most :-) If you're honestly worried about having a job and aren't confident in yourself, learn Java. It might die tomorrow (who knows?) but I've seen mountains of code and somebody's gotta maintain that or at least translate several years from now. Not the most glorious job but it would certainly pay the bills. The language is still in use and I've seen people hired by simply writing "Expert in Java" on their resume (whether it was true or not).

    Is it a better path to focus on moving into management?
    The company I work for is unique in the respect that I am allowed to grow on one of two paths. One is a functional manager that has many people reporting to them (think Lumberg from Office Space). The other is a technical leader--one with degrees & experience implementing ideas. The latter is actually the kind of leadership I desire to fulfill. While it may be more difficult to pursue this "other" kind of management, I hope a lot more companies offer pay equivalent to their technical leaders and recognize them as being just as important as your traditional managers. Technical leaders are the Chief Engineers on projects, the "go to guys" in any scenario where you have technical questions/problems, the subject matter experts, the scientists. The traditional path are the project managers, the leaders who never have to prove themselves, the people who protect you from upper management and who, eventually, become upper management. If I ever found myself interviewing for another company, I would definitely ask them about positions available for technical leaders and, from the sound of your question, this may be something you desire also.

    Choose your path wisely.
    --
    My work here is dung.
    1. Re:The Fileds You Love by scoove · · Score: 4, Interesting

      One is a functional manager that has many people reporting to them (think Lumberg from Office Space). The other is a technical leader--one with degrees & experience implementing ideas.

      There's also a third option in many larger companies: a cross-functional, multi-domain expert. While many people are familiar with the Java/Routing/InfoSec/DB2/etc. expert who has developed extensive expertise and attained mastery in the technical domain, the multi-domain expert is another option which can be quite professionally rewarding.

      Both my brother and I had IT careers (he in client app development and me in infosec and internetworking), and both of us went back to school. He added a marketing undergraduate and a MBA with a marketing focus, while I added a finance undergraduate and a Master of Science in Economics. For both of us, it was an exceptional career move. He's a marketing information systems manager for a Fortune 500 company, handling most of the IT projects for the different product brands of the company and gets to work with developing them the way he wants for his clients - architecting the solution, developing cross-functional dev teams, etc.

      The finance and economics addition to an infosec and networking background has helped me become a dual-domain expert in operational risk management (an area that needs many more experts who understand both IT operations and the whole quantitative aspect). I get to design and develop metrics that help us analyze, track and improve our operations, manage the development of the systems that collect and report these metrics and then evaluate them to assess the company's global risk.

      The cool part is if you like to set yourself apart from the crowd, it's a great way to accomplish that. It certainly isn't easy committing time to develop that second domain, and takes very careful job selection to get into a place where you can start using both domains. However, because companies seem to have serious problems communicating between different functional areas (e.g. marketing can't speak IT, and IT can't talk marketing), people who span the gap get very nicely compensated, have significant creative authority and overall get to see their ideas implemented.

      *scoove*

    2. Re:The Fileds You Love by dankney · · Score: 4, Funny

      I get to design and develop metrics that help us analyze, track and improve our operations, manage the development of the systems that collect and report these metrics and then evaluate them to assess the company's global risk.

      And use enough buzzwords to make the tech implementer roll their eyes and mock you behind your back. . .

    3. Re:The Fileds You Love by scoove · · Score: 3, Insightful

      And use enough buzzwords to make the tech implementer roll their eyes and mock you behind your back. . .

      It only sounds like buzzwords because you probably don't work with it. That's what we call quantified measurements, and those in operations management, finance, risk management, etc have to do that to really get at a problem. Otherwise we're practicing the behavior you're inferring by your comment: making totally subjective, qualitative guesses.

      A good piece of advice is not to mock someone for using language you don't understand, especially if it sounds like management speak. If you're going to represent more than one domain, you have to stop talking the geekspeak of your locale and be able to represent concepts in the dialect of the group you're working with. It does me no good to go rambling about GARCH models and problems with autoregressive conditional heteroskedasticity in my time-series dataset, but that's ineffective and inappropriate.

      My job is to apply my expertise to find solutions for my clients, not to wow them with big terms. Nobody cares that you can talk fancy words in your area of expertise. They assume you know your stuff - that's why you're there to do the job. Whenever you work out of your locale, communicate in their language and you'll find you're much more effective.

  6. Tech Support by cralewyth · · Score: 5, Funny

    I hear it's lovely over at tech support. You get to talk to n00bs all day and make them run around in circles because it's the "fixing ritual" and stuff.

    No seriously. BOFH is the field you're after.

    --
    "Women are just like ninjas; They lie even when it is more convenient to tell the truth." ~ Unknown
  7. Re:Good techies don't necessarily make good manage by Nerdfest · · Score: 4, Insightful

    Where I work, the opposite tends to happen. If you're not that good technically, you tend to bubble up to management. I'm not saying they're complete idiots, just that they're not the best technical people. I still don't think it's the best way to find good managers though ... they may suck at that as well.

  8. Wrong Question by LibertineR · · Score: 4, Insightful
    The right question is: "Which area of IT do you LOVE?"

    Almost all areas are 'hot', but that doesnt mean anything. The one that will STAY hot for you, is the one that you love enough to continue your education throughout your career, and dont just pick someting to do for a paycheck.

    If you love a particular area, your constant learning and improvement will lead you into related areas and keep you relevant throughout your career, you can move into consulting, writing and development within your chosen area and never miss a beat.

    Never chase a paycheck.

    1. Re:Wrong Question by Cytotoxic · · Score: 3, Insightful

      Listen to LibertineR, he knows what he's talking about! Always do what you love. You'll be passionate about it and you will do well. There are way too many people in IT because they they heard that there are a lot of good jobs available, rather than because it is their calling in life. Finding out what you love to do is easier said than done, but it is the secret to success. (and if what you love is money, then go into sales or start your own company - that's where the money is, not management)

    2. Re:Wrong Question by Cederic · · Score: 4, Insightful


      Sadly, no.

      I went into IT because I love programming.
      I evolved into Software Engineering because it made the programming easier.
      I learned how to design because you can't do SE without it.
      I became an architect because I had to design beyond my immediate system.
      I got frustrated by the shortsightedness of the people giving me projects and became an enteprise architect so that I could influence the broader picture.
      I expect to find I lack sufficient authority and move into IT director type roles to gain that ability to make the decisions I feel are necessary.

      I still love programming. I just couldn't take a programming job any more. I'd get too annoyed at the crap development processes, the poor design, the inadequate architecture, the incompetence of the business and the inability to change things at a high enough level.

      So find an area you love, yes. But expect it to change. Go with the flow. And remember the advice from Ferris : Stop and take a look around once in a while.

  9. Doesn't matter by Anonymous Coward · · Score: 4, Funny

    Any provided you live in India. Gotta love cheap phone support.

  10. Cisco Voice by eggoeater · · Score: 4, Informative

    One area that is rapidly growing is Cisco VOIP. I've been studying for my Cisco CCVP cert and it's more complicated than you might think. Most companies love the fact that they can use their existing network equipment (routers/switches) to replace all their PBXs/ACDs, not to mention free inter-network calling.

    I work for a large company and we're currently in the process of a ~5 year migration from all legacy PBXs to Cisco Call Manager. Many other companies are doing the same. Just about all new offices are built with either Cisco or Avaya VOIP systems, but most companies go with Cisco since you don't have to be concerned with compatibility. (eg. A high-end Cisco router is also your telephony gateway where the T1s are converted to VOIP.) As you can guess, this calls for some highly specialized skill sets (eg. Call Manager/ICM/IVR + Cisco Networking/IOS, etc.) which not a lot of people have. If you're certified, you will NOT have a problem finding a job.

  11. Pick something boring, or get lucky by Overzeetop · · Score: 3, Interesting

    Seriously. Some of the worst jobs have great security and pay well. Look at COBOL programmers - it's probably better to say you're a piano player in a whorehouse than to admit you mind legacy COBOL installations, but I hear that they're pretty darned good jobs. The "coolest" jobs usually pay squat, have lousy hours, are highly competitive, and experience high burnout. (see: Elelctronic Arts).

    On the other hand, you can always pursue what you really love, and hope that you happen to get lucky and that your obscure interest is the Next Big Thing (TM). That's how the really great ones did it. Of course, if you did a better job selecting your parents (see: Paris Hilton), the career thing wouldn't really be an issue and you wouldn't be in this boat. So based on your track record, going with the chance part isn't such a good idea for you.

    --
    Is it just my observation, or are there way too many stupid people in the world?
  12. Avoid "hot" careers by Pope · · Score: 4, Insightful

    Today's "hot" career is tomorrow's outsourced to India dead-end job. Stop caring what's popular and focus on what you like doing the most. If you like doing all sorts of different things, then keep on doing that!

    --
    It doesn't mean much now, it's built for the future.
  13. Loaded question by t00le · · Score: 4, Informative

    I think the question is somewhat loaded, but I suppose everyone has a perspective. In my opinion VOIP and Network Security are hot career paths. I have been working with both (Cisco) over the course of the last five years and the market is very good for specialized Network geeks. When looking for marketability on the job boards VOIP/NetSec are paying more than my other skills.

    The one thing I do know for a fact is if you are diversified in a couple of "hot skills" your marketability goes through the roof. If you throw management experience along with that you can make some pretty hefty sums AND find a job you like.

    My .02

    --
    When the only tool you have is a hammer, every problem looks like a nail
  14. Re:Good techies don't necessarily make good manage by dlZ · · Score: 5, Insightful

    I have to agree with this. I'm a business owner, with a partner. I'm the hardcore techie here, while my business partner has a background in video production and marketing. He tends to take on the true management role here while I worry about actually getting the work done. It works out well as I'm not a great manager but I can get the work done when it needs to be.

    The thing I have noticed is that a lot of people in a more technical role feel that they would be better in charge but in reality would probably just hate the position. I love being in control (hence owning my own business) but at the same time I'd rather leave the more managerial duties up to my business partner while I really worry about the technical side of things.

    I have been a manager at a few places and while I did a decent job and my staff liked working for me, but I didn't enjoy the role as much as I enjoy being in the forefront with my technical skills. I did learn a lot about running a business from these positions which is a benefit now, though, and don't regret having been a manager. I just didn't enjoy it.

    --
    rm -rf ./evidence @ punkcomp
  15. Re:Choose a career you like by l0rd · · Score: 4, Insightful

    Exactly,

    One thing I miss about the good old days when anyone who even looked at a computer was considered a nerd was that you didn't get these kinds of questions. The words IT & career in the same sentance just bring a foul taste to my mouth.

    Sure, if you just want to make a living IT is an industry that will probably always have a job for you. However if you aspire to become a master at something it has to be something you live & breathe. Just figure out what you like doing and roll with it.

    You like organizing people become a manager. You like helping people work at a helpdesk. You like figuring out how computers work get a job making device drivers. You like php become a web developer... You get the idea. Doing something just because it's hot is a sure recipie for disaster.

  16. Get out of IT by Anonymous Coward · · Score: 4, Funny

    If you are having this much doubt about what you want to do, for Gods sake, get OUT of IT.

    Go into the resturaunt business. run a mcDonalds. Get into the auto mechanic shop business. You can probably make better money herding 10 people cleaning houses. (That right there is a six figure a year job, for basicly managing a crew of people who descend on a house, clean, sweep, vacume and leave, repeat ad infinitum, scale as large as you want)

    Of course, considering your lack of direction, you may not be the best person to run a business. Perhaps you should stick to help desk.

  17. AUDITING by kalpol · · Score: 4, Funny

    Oh yeah...I'm coming for all your asses.

    --
    12:50 - press return.
  18. I am an IT Multi-Tool by Dareth · · Score: 3, Interesting

    I have the same problem. I am an IT Multi-tool. I am not the best tool for any particular job, but I may be the best and only tool you currently have for the job at hand.

    I have the following credentials:
    Degree in Computer Science - No I didn't learn everything I needed to know in college, but that paper opened a few doors.
    10+ years experience with computers in a networked environment.
    Experience using and troubleshooting computers ranging from DOS to Windows to Linux, with a sprinkle of Unix.
    Programming in C,C++,Java, VB and VBA
    Knowledge of HTML
    Experience in maintaining production servers for critical tasks.
    Experience with peer-to-peer networks, hundreds of nodes.
    Experience with Databases,MSSQL and MySQL know basic to moderate level SQL.
    Experiences with Apache and IIS.
    Command line scripting from DOS Batch to Linux Bash. ...
    Tons more things I have just "worked" with as needed.

    I have always been a "jack of all trades" in terms of computer work. Recently I have been specializing, not by choice, but by necessity in Phone and Data Networks. I have taken several weeks of training in ACD and Phone PBX systems. I have been setting up our phone ACD for about 2 years now. About to start working closer with the PBX hardware as well. It is an interesting niche.

    If you are just looking for the latest "hotness" in computers it is security. But that type of job could well leave you stressed out with gray or no hair and a coronary in your early 40-50's. I see too many green newbies fresh out of college all excited about security and their careers. I don't know if I should find them amusing or scary. I guess someone has to do that job.

    As for me, If I can keep learning and enjoying what I do, I couldn't ask for anything more.

    --

    I only look human.
    My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
  19. Re:No Future in IT in USA by BadERA · · Score: 5, Interesting

    Somebody's bitter.

    I was bitter once. I got laid off after 9/11, couldn't find a job to save my life ... or, rather, my car.

    You have to bounce back -- if you don't, you shouldn't be in the field to begin with. Same thing applies if you can't find a job today -- you probably need a new profession. IT is booming, the Internet bubble was a temporary setback. Not all IT is INTERNET.

    Not everything can be offshored -- I've seen successful offshoring, but I've also seen a large number of disappointed businesses who feel they were overcharged for sub-par return on investment in off-shored projects.

    There is always a need for business analysis and system architecting. Someone thousands of miles away is going to have a very difficult time truly knowing a business, and understanding its needs. There is ALWAYS going to be a need for capable, creative people who know the technology AND the business to be local.

    --
    I am, therefore you think.
  20. Re:Good techies don't necessarily make good manage by ElForesto · · Score: 4, Interesting

    Amen to that. Far too many businesses promote someone to management because 1) they're been there for a long time and 2) they're good at their technical job functions. They don't, however, have a lick of personnel or project management skills. It also usually ends up taking someone from a job they do well and putting them in a job they do poorly, a double whammy. I'm at least smart enough to know that I shouldn't be given anything beyond a team lead position.

    --
    There is a difference between "insightful" and "inciteful" other than spelling.
  21. Stupid question by __aahlyu4518 · · Score: 3, Informative

    Go with the job that you LIKE. Not what is the best for a career.

    A career in which you don't feel at home with will kill you before you get to retirement.

  22. Re:The Fields You Love by gfxguy · · Score: 5, Interesting

    I disagree. I'm a "jack of all trades, master of none" and I'm well paid. That means I'm pretty much stuck in my job unless I want to take a huge paycut.

    It started off as a specialty position (graphics), and I was well paid for it. But it turned into a position where I was responsible for a lot of other, varied things, like the intra-departmental website, and eventually my grasp of modern graphics technologies started slipping.

    Now, because it started off paying so well, I'm still paid well... but now my raises are crap, not enough over cost of living to make any difference. I while I like the company I work for, I hate the location, and would take an equally paying job (adjusted for location) just about anywhere else.

    The problem is that when I look at available jobs, the ones that pay even moderately close to what I'm getting now require a specialty.

    This really kills me - because I'm sure I could get a great raise here if I threatened to leave, but I wouldn't threaten to leave unless I could follow through on it (I'm not good BSing with empty threats).

    So, OK, I'm giving my annecdotal experience, but I find it's true elsewhere. I've had this conversation with my manager and he agrees, and he'd like to see me be able to get back into graphics 100% of the time, but the company won't budget for another programmer (I'm in a unique position here). I like all the things I'm doing, but I wouldn't mind dropping the variety and concentrating on being great at one or two things, I'd still be happy and I'd be able to demand more at a different place.

    --
    Stupid sexy Flanders.
  23. Re:Good techies don't necessarily make good manage by aadvancedGIR · · Score: 3, Informative

    Actually, I beleive the Dilbert principle is more accurate in the GP case : "The least competent ones are promoted first to take them away from productive position where they could be dangerous".

  24. Re:Good techies don't necessarily make good manage by bjd145 · · Score: 5, Insightful

    From what I've experienced again and again and again is that one of the reason (and there can be others) that techies don't make good managers is that they try to live in both worlds. The new techie manager still wants to get his hands dirty doing the day to day work. Part of this is that they are don't trust others to do it "right" or they are afraid of losing their technical skills. The new techie manager never really gives him/her self over to the dark side of management.

  25. Smart people are still in demand! by ErichTheRed · · Score: 4, Interesting

    A lot of people disagree with me, but if you want to stay technical, chasing the latest specialty is not always the best way to go. If you really want to build a technical career that will last you through outsourcing, technology shifts, etc., then you need to have a broad background.

    Smart people will always find work. I've bounced all over the IT world...support, sysadmin, design and architecture, and it's really hard keeping your skills truly sharp. Someone who's truly valuable picks a few key areas to get really good at, and knows _something_ about the rest. If you're a network guru, learn a little about the machines you're connecting. If you're a systems genius, learn enough about databases to realize your DBA is BSing you. :-)

    Take the latest fads...SOA and security. You can learn everything about these two areas, but what happens to all that knowledge when it becomes a commodity? When the execs realize SOA is just a rehash of centralized computing with some XML and the web thrown in, where will you be? Keeping yourself open keeps you employed.

    I learned through a really tough experience that management was not for me 2 years ago. Technical people generally don't make good people-managers. It's not lack of social skills, but management is a completely different job. You will never touch a machine again. You will be in meetings, answering e-mails, making phone calls, and "separating the kindergarteners" when they get into conflicts. If you burn out on technology, then it's an excellent career path. Otherwise, don't let people convince you it's a good move. Rememeber all the bad bosses you have/had? Just like some people aren't suited for IT, they're not suited for managing either.

    One good overspecialization example I like to cite is OpenVMS system administrators. OpenVMS is still in active use, but it's really declining. Truth is, it's easier to write new applications to run on Linux/Windows Server than to pay for expert system administrators. One of the first IT jobs I had before moving on was VMS support. I don't know how DEC trained these guys, but they're some of the best, most vigilant admins I've ever seen. However, finding a paying job working with those systems is getting harder. I world love to have that kind of sysadmin in the Linux and Windows world I work in, but a lot of them are totally specialized and don't want to learn new systems.

    One other thing...outsourcing is here to stay. If you're a developer, become a crack genius developer so you can get the contract jobs rewriting outsourced code that doesn't work. If you're a procedural system admin, become an operations wizard that designs systems that don't randomly blow up. In short, truly earn your money!

  26. Re:No Future in IT in USA by slartibart · · Score: 3, Informative
    Sorry but this is not as true as you think.

    When you hire someone to program for you, communication is absolutely crucial to success. If the person you hire doesn't speak the same language you do (or doesn't speak it well), you're probably not going to get what you ask for. Also consider how bad communication will be if you are unavailable (sleeping) most or all of the time they're working. You can only communicate once per day. If they have a question, they have to stop working until the next day when you've answered them.

    A good portion of the time, outsourcing is just not worth it. It doesn't matter how cheap the labor is, when the product you end up with is not what you want.

  27. My advice by finkployd · · Score: 3, Insightful

    I've had a pretty successful career, totally by accident, so here is my advice.

    Do what you enjoy. That's it.

    Everyone I know in IT who really enjoys what they do (to the point where they would probably do it as a hobby for free if they were independently wealthy), ends up being successful. They are passionate and competent, likely not because they are inherently smarter than anyone else, just that they spend more time learning, experimenting, and playing around with the technology they like and work with.

    I also know people who picked their IT career (and decided to go into IT to begin with) based solely on the job market. Will I make more money with .net or Java? Are the more jobs available for an Oracle DBA or a Microsoft SQL DBA? If that is your primary consideration then you will probably be beaten out by the people who are passionate about their career choice and made it for other reasons. Honestly if you are really excited by databases (you sick bastard) then you should be interested in working with all of them and learning as much about both DB theory and the specific implementations as you can.

    There are jobs out there for everything. If there is something out there that really gets you excited go for it. If you learn quick, really throw yourself into it and know your stuff, you will find employment. It might be more lucrative in the short term to trend hop, but if all you are interested in is the possibility of making big bucks then you should forgo IT and go into something like hedge fund management.

    Me? I really dig identity management stuff. I've worked in academia with SAML, Kerberos, and PKI and in the corporate world with Oracle and Sun's IdM tools. A word of warning though: Find a field you enjoy, but do not get too hung up on a specific technology. I'm happy using my knowledge and experience in IdM to work with Infocard, SAML, PKI, LDAP, NIS, Xellerate, CoreID, Kerberos, AD, etc. I have my opinions as to what is best for what need, but I try to not be too much of a snob about it and limit my career that way. I've seen a lot of people go the "horse and buggy" way by latching on to a specific technology and refusing to let go when the world moved on.

    Finkployd

  28. Re:The Fields You Love by ThomsonsPier · · Score: 3, Informative
    Hmm. It seems that most people don't know the full saying:

    Jack of all trades,
    Master of none;
    But oftentimes better
    Than master of one.

  29. Re:My Faustian deal by FlavorDave · · Score: 3, Interesting

    I'm in healthcare IT too, its as close as I can get to blood without getting queasy.

    I was a developer for 10 years before I decided to work as a DBA exclusively. When I developed I was always the DB "go to guy" because it was always something that interested me. I wanted to make sure what I delivered performed well and the DB was a big part of that.

    I enjoyed software development immensely but I got tired of the death marches and feature creep. One of my CEO's was nicknamed "Two Week Pete" because after visiting a customer he would always promise some 6 month feature in 2 weeks. I still develop software but just the 'fun' stuff mostly personal and open source projects. I'm the only DBA here that has Design Patterns and OO Software Engineering books right next to my SQL references.

    While there is a lot of minutae involved in keeping a large DB instance running, generally my requirements are "We need an instance to support X amount of load and we need it by date Y". When I was a software developer I enjoyed producing elegant code. Now that I'm on the DB side I am responsible for producing elegant solutions which include hardware, software, and services. Yes, when its bad its bad. I usually have a couple of bad weeks a year where I get little to no sleep. I use the 'off time' to keep things running as smoothly as possible and try to reduce the episodes of nightmare performance.

    It has been good to have a taste of both sides though. There are a lot of developers that are clueless about the DB side of things and a unfortunately a higher percentage of DBAs that have no idea what goes into developing a decent client or middle tier.

    -- Dave

  30. That IS the "dark side" of management. by Valdrax · · Score: 5, Insightful

    The new techie manager still wants to get his hands dirty doing the day to day work. Part of this is that they are don't trust others to do it "right" or they are afraid of losing their technical skills. The new techie manager never really gives him/her self over to the dark side of management.

    You see, that IS the real "dark side" of managment -- when you become a micromanager or some other type of manager that constantly second-guesses their employees because you "know better." Even worse is the type that is constantly trying to make people prove themselves to them by withholding information to see if their subordinate is "smart enough" to come to the same conclusions (and then berate them if they don't either due to a difference of opinion or a crucial missing piece of information).

    I've had four jobs since I entered the IT field. Every single manager I've had was a former programmer with the exception of one boss's boss (who was entirely awful because she was more interested in office politics and backstabbing for advancement... but I digress).

    All the good bosses I've had gradually abandoned the programming side and learned to act as mentors. They used their knowledge of the system to give pointers on where to look when you were stuck on a problem and trusted you to get things done, only prodding every now and then when a schedule was threatened. All the bad bosses I've had (save the one mentioned above) second-guessed you constantly and either went around your work to put someone else on it (like themselves) or constantly made you justify ever single moment you spent your day on. In both cases, the attitude comes from the thought that they could do it better if they didn't have to do all this management crap instead.

    In other words, the secret to going from a technical role to being a good manager is learning to let go. Use your skills and knowledge to aid your subordinates and shield them from upper management by understanding what they are doing. If necessary, use you knowledge to call their BS if they're actually slacking, but don't envy them or treat them as irritating time-wasters blocking you from doing "your real job." Otherwise, you're just demonstrating the Peter principle.

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
  31. Yes, but... by wonkavader · · Score: 3, Insightful

    Small shops should and do love JOAT folks, but they may have trouble hiring them.

    If a shop is large enough to have an HR department (complete with screeners) it's hard to get a foot in. It's often difficult to get a position open to hire for with the designation Jack of All Trades. Uppers don't understand, and HR certainly doesn't. (Thats a common situation, but not a rule.)

    If they do get that designation, starting salary for the job will be somewhat low, because that designation will be of lower status than an "expert".

    And small shops tend to pay less than big ones in the first place.

    This wouldn't apply at all for a shop consisting of just one or two people, but then, they tend to pay VERY low salaries.

    For the record, I'm a JOAT, too, but have been involved in a bunch of hiring.