IT Skills Shortage? No, Just Looking in the wrong place

  • Comments posted to this topic are about the item IT Skills Shortage? No, Just Looking in the wrong place

    Best wishes,
    Phil Factor

  • I look at the DBA roles as generally the production or support role. Then the development DBA's and a small chunk of QA DBA roles.

    The support DBA works on the day-to-day applications to make sure they are up and running. If the DBA works for an end user company he's going to interface with the SW production company to find out the cause of the error. If the support DBA for the SW company the responsibility is to figure out if the error was caused by a SW feature or end user error.

    The dev DBA does the building of SPs, functions and such to automate the process.

    The QA is the in-between that doesn't let crap get to the end-user.

    Where the problem seems to come in is that you have a bunch of developers that think it is faster to grab 3K rows in a hundred column table of millions and process it RBAR rather than ask the DBA "Can we get these 25 rows by feeding in these parameters."

    I've seen it done in the past, and I'm sure I'll see it again.



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.

  • "As well as computer scientists, I know of several DBAs who were once professional musicians, actors, hairdressers, artists, scientists, athletes, soldiers and even solicitors and architects. They all make good DBAs too. If only developers were able to bring such a range of skills, experience and knowledge to the job!"

    The trouble is, not everyone can program. I'm a developer, and I've met many people in IT that by their own admission cannot program in any language - and I've certainly encountered developers that really should be doing something else! Your statement, quoted above, implies that anyone can become a DBA πŸ˜‰

  • I have a conspiracy theory about the so-called "IT skills shortage" : it's just a ploy to get more people into IT in order to increase the pool of job applicants so salaries will decrease. The public perception of the "problem" would be very different if it was called the "IT high salary problem".

  • calzakk (3/30/2014)


    "As well as computer scientists, I know of several DBAs who were once professional musicians, actors, hairdressers, artists, scientists, athletes, soldiers and even solicitors and architects. They all make good DBAs too. If only developers were able to bring such a range of skills, experience and knowledge to the job!"

    The trouble is, not everyone can program. I'm a developer, and I've met many people in IT that by their own admission cannot program in any language - and I've certainly encountered developers that really should be doing something else! Your statement, quoted above, implies that anyone can become a DBA πŸ˜‰

    No, it doesn't. It means many DBA's have varied backgrounds, some of which have nothing to do with IT or technology. And yes, there are some people who should not be allowed to write a line of code, but I have met people like that who can architect a system exceptionally well but couldn't write the underlying code worth beans.

    Not everyone can develop code to meet requirements.

  • "As well as computer scientists, I know of several DBAs who were once professional musicians, actors, hairdressers, artists, scientists, athletes, soldiers and even solicitors and architects. They all make good DBAs too. If only developers were able to bring such a range of skills, experience and knowledge to the job!"

    The trouble is, not everyone can program. I'm a developer, and I've met many people in IT that by their own admission cannot program in any language - and I've certainly encountered developers that really should be doing something else! Your statement, quoted above, implies that anyone can become a DBA

    It implies only that good DBAs come with the hard-won ability to find out and learn new skills rapidly. Despite their wide range of backgrounds, the DBAs and Database developers I respect are 'quick on their feet' to acquire new skills. In a sense, anyone can become a good DBA, no matter their background or experience, but it takes a great deal of work and application to get there. One of the best DBAs I ever worked with, and one of the most expert, had once been a champion weightlifter and policeman who specialized in responding to violent incidents. He was brilliant at moving servers around and we always got served first in nightclubs. His background gave him the tenacity and determination that he applied to learning the role of DBA. The sight of him marching grimly towards me after I'd done a small but necessary modification to a production server is one I shall carry with me to the grave.

    Best wishes,
    Phil Factor

  • The IT skills shortage is just like the so called plumbers shortage we had 10 years ago. A government initiative pushed teenagers into training as plumbers at the colleges, but when they had passed the basic qualification there were no jobs or places available for them to complete the on-the-job part of the qualifications. Most gave up plumbing and felt the time had been wasted, including my nephew who now repairs computers.

    And also to break the stereotypes our development team is mostly 50 plus and female.

  • Phil Factor (3/30/2014)


    Despite their wide range of backgrounds, the DBAs and Database developers I respect are 'quick on their feet' to acquire new skills.

    Wow this really rubs me the wrong way! I guess we value different things and you wouldn't respect me, luckily I don't obsess over acceptance from strangers :crazy: πŸ˜›

    I know some DBAs who fit your profile, they can learn a lot of technical minutiae rapidly and retain it to bring up in meetings ad-nausea. I'll admit it's a very cool and unique skill to have but in my experience those same people are usually also: extremely abrasive, create bug-riddled code, don't care about formatting or documentation to the point of making everything unreadable and unmaintainable, and every task seems to become an exercise in obfuscation and job security.

    But management loves them because they answer, "Yes", to everything! They're heroes, constantly putting out the fires they themselves have caused in production from their arrogance πŸ™‚ I can't say I don't respect them, I do, in many ways, but ... not every way.

    If I had to specifically single out some criteria for respect, it would be the methodical DBAs who tick the boxes properly; I don't care if it takes someone longer to learn something because learning shouldn't be treated as a competition. I would hazard a guess that they are more curious about testing and understanding the "why" of things and hitting them with hammers until they click... as opposed to reading one article after another to pass another certification and boast about how smart they are.

  • Cody K (3/31/2014)


    I do knows some DBAs that fall into your criteria of learning a lot of technical minutiae quickly and even retain it. That's a cool skill to have. But they are usually also extremely abrasive, create bug-riddled code, don't care about formatting, and every task seems an exercise in obfuscation and job security.

    Nice generalisation there. I'd write a longer comment, but I have some bug-ridden, poorly formatted, obsfucated code to go and write... :Whistling:

    The best database people I know (and not all of them are DBAs, a good number are developers) learn fast, learn details and take a great deal of pride in their work, which means well-written, well formatted and well documented and a desire to help others learn and improve.

    Bug-ridden, poorly formatted and uncommented implies to me at least that someone doesn't care about their job (and it doesn't matter what they say, their actions are what count)

    btw, job security, in the way you describe it there, means 'can't take vacations, can't get promoted/transferred'. To hell with job security.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • GilaMonster (3/31/2014)


    Nice generalisation there.

    It is a generalization, speaking from limited experience, and open to discussion. I'm sorry if you felt I was saying, "every fast learner is like this". Especially not you... because you're amazing πŸ˜€

    I guess my argument is with the idea of correlation between fast learning and every other quality you and I listed. Between, "I want someone who learns fast!" and "I want someone who does their job properly!" I know which one I would pick.

    If someone is doing their job well, why would it matter if it took them a few extra days to learn something?

    Bug-ridden, poorly formatted and uncommented implies to me at least that someone doesn't care about their job (and it doesn't matter what they say, their actions are what count)

    Funnily enough I don't see it that way. And I feel that those people love their jobs.

    They just have different motivations and values to you or me. They love feeling important, management admires them for always getting the job done "quickly", looking very busy, and communicating with everyone about how they just put out another late-night fire (leaving out they caused it).

    I don't think it's healthy, for them or the business, but those people certainly seem to be everywhere and it's not for me to judge.

    On the other hand I get my job satisfaction from the feeling of implementing a logical, robust solution, on clean data, and the aesthetics of beautifully formatted and easily maintainable code. I'm probably crazy but that's what I care about and what makes me smile.

    But I don't think I "love" my job more than them. The job, to me, is secondary. I suspect the job is secondary to them too. We're all getting different stuff.

    btw, job security, in the way you describe it there, means 'can't take vacations, can't get promoted/transferred'. To hell with job security.

    Here here. One of our developers came in sick for a week having lost their voice, and has now taken a month holiday with a brand new company laptop and sim card... to get some urgent work done. To me that's atrocious.

  • I’m always fascinated to talk to DBAs about their backgrounds. Somehow, DBAs have escaped a lot of the stereotyping, and because of the many different ways that they’ve entered the profession, we have a healthy diversity of background and previous experience. As well as computer scientists, I know of several DBAs who were once professional musicians, actors, hairdressers, artists, scientists, athletes, soldiers and even solicitors and architects. They all make good DBAs too. If only developers were able to bring such a range of skills, experience and knowledge to the job!

    This has started a rolling stone of generalisations. Here are my points and experiences to fuel the fire:

    • DBAs are often stereotyped as being even more socially inept than developers. (Please note that I don't believe this. I am just reporting that I have come across this.)
    • I have met developers who have been (and sometimes continue to be) professional musicians, actors, artists, scientists, athletes, soldiers, pilots, solicitors, civil engineers, builders etc. It is an industry wide phenomenon that I attribute to the low entry bar.
    • The value of the varied backgrounds depends on the individual's nontechnical skills and abilities that they bring with them.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Cody K (3/31/2014)


    Funnily enough I don't see it that way. And I feel that those people love their jobs.

    I would disagree. If you love your job (which involves supporting the business), you take time to do things right, properly, even if it takes a little longer. I think (and I've worked with some of this type myself, what they actually love is:

    They love feeling important, management admires them for always getting the job done "quickly", looking very busy, and communicating with everyone about how they just put out another late-night fire (leaving out they caused it).

    They love the recognition, the prestige, sometimes to a point where they ignore good practice (like proactive monitoring) because such practices reduce the opportunities for being a hero.

    One guy I know locally, he refuses to read blogs, articles or forums because "I know what I'm doing, there's no value in blogs". Never had to work with him (fortunately)

    Here here. One of our developers came in sick for a week having lost their voice, and has now taken a month holiday with a brand new company laptop and sim card... to get some urgent work done. To me that's atrocious.

    Agreed.

    I work very hard not to be indispensable. If the company is in crisis any time I plan a vacation, there's a problem. Been there, done that, was made redundant without so much as a "thank you"

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • GilaMonster (3/31/2014)


    ...

    Here here. One of our developers came in sick for a week having lost their voice, and has now taken a month holiday with a brand new company laptop and sim card... to get some urgent work done. To me that's atrocious.

    Agreed.

    I work very hard not to be indispensable. If the company is in crisis any time I plan a vacation, there's a problem. Been there, done that, was made redundant without so much as a "thank you"

    I think that I provide the most value when I ensure that I am not indispensable. I think that paradoxically it makes one more indispensable as so many people do not do that i.e. you have to hang on to those who make themselves replaceable as not enough people do that.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • "If only developers were able to bring such a range of skills, experience and knowledge to the job!"

    Wow, nice job generalizing and bashing an entire profession. Thanks for the insult.

  • Whenever an organization needs to build the next version of the platform or leverage some new technology, executive management complains that there is a shortage of software or database engineers. So they look externally, but once they actually hire a couple more developers, they either let them go six months later due to budget constraints, or the developers leave on their own because they are bored with not enough work to do after the project is completed. Maybe those of us in IT just need to get smarter and wear more hats. Sure, the industry could use more IT people, just like we all think we could use a live in house maid, but ultimately we can't pay for them.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Viewing 15 posts - 1 through 15 (of 28 total)

You must be logged in to reply to this topic. Login to reply