Ageism in IT?
Embedded Geek writes "It's hardly a new topic, but BBC is running a story about ageism hitting Gen-X, especially in IT. As a 34 year old coder, I was horrified to hear a quote from a *hiring manager*: 'In the IT sector (and coding in particular) younger minds generally work faster -- I would rather employ a keen teenager who code programs computers quickly than an older person.' It didn't help that the person is 32 years old. My kneejerk reaction, the same one anyone else over 30 would have, is that the guy is a buffoon (I'll withhold my preferred, spectacularly vulgar, term). The problem is that I do not believe his idiocy is unique - I have definitely felt the vibe when interviewing. It's frustrating, since Gen-X is finally shedding the media hyped 'slacker' stereotype only to run headlong into this garbage. Have any other Slashdot readers seen this? What is the youngest you can be before some PHB declares you fit for the scrap-heap? Other than stocking up on hair dye and botox, what steps can I take to prepare for the future? Share your war stories here." Ask Slashdot handled this topic over two years ago. Of course, this behavior could be explained away as economic concerns, as the decision to hire younger (and typically cheaper) employees can directly affect the bottom line. However, one has to wonder if the decision to go with less experienced programmers also affects software quality, in the long run. What are your thoughts on this subject?
I don't think that the ability to learn is determined at all by age. I believe that nearly anyone can learn how to code at nearly any age. But I would liken this ability to that of playing a piano.
Sure, an older person can pick up the ability and wield a certain prowess and even artistry. But no one, to my knowledge, would argue the fact that a person who learns to play the piano in childhood has a certain "feel" for it that people who pick up this ability later in life can never attain. It's not that the older person can't play sonoriously with rhythm and emotion. But the younger player has a certain reach that will never be known to the older guy.
Andy Hertzfeld (of the original Macintosh development team) claimed that he used to be able to track and house far more complex contructs of thought, and more of them, in his mind when he was in his early 20's than he ever could at the time he was giving the interview (I would guess he was somewhere in his mid forties at that time). He called this ability "the gift of the young".
But in the book Hackers: Heroes of the Computer Revolution [barnesandnoble.com] Steven Levy described how Ken Williams, the founder of Sierra Online [sierra.com] felt a missionary zeal in converting people to the belief that learning how to program a computer could change your life. Ken met Bob and Carolyn Box, who were an older married couple in their fifties. Bob was "...a former New Yorker, a former engineer, a former race car driver, a former jockey, and a former Guinness Book of WOrld Records champion in gold panning." When they both tried to get a job working for Sierra, Ken told them to "put up something on the screen using assembly language in thirty days". According to how the story is told, they both became very able assembly language programmers. Roberta Williams (Ken's wife) considered the Boxes "inspiring" and felt that learning how to program "rehabilitated their lives".
Of course that was a long time ago, and thus far I have spoken only of the abiltity to learn and to become an able programmer. To get slightly more "on topic"; as to whether there is job market opportunities for older folk, there is no reason an employer should discriminate on the basis of age, though I'm sure that many do. But as for the pure concept of programming I myself only picked up some ability in C++ (on my own, not through any school) when I turned 30 as I realized I was getting older and it was basically "now or never". I still enjoy learning as much as I can about it, and consider it a wonderful intellectual exercise, though I have no concrete plans of doing it for a living. I've already got a stable professional life and see it as a very enjoyable and rewarding hobby.
Quod scripsi, scripsi.
Or a new bunch of people becoming old enough to experience it. I'd feel worse about it if the people who are starting to experience age-based discrimination weren't the ones benefitting from it a few years ago.
'I ain't a liar, baby, and I ain't proud I just want what I'm not allowed.' -- Violent Femmes, 36-24-36
Give me a seasoned vet who has the depth and breadth of experience to have learned all of those "only happens once every x years" type of lessons over some young, fast coder who has yet to learn these lessons.
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Its easier to sqeeze 80+ hrs out of someone with out kids, house and a wife.
With all these old folks posting on Slashdot? Don't they know it's a site for young people? Sheesh, go hang out on cnn.com, grandpa.
As a respectable web pornographer I would have to say that when we consider subjects for our titalating erotic material, or as the 31337 call it, pr0n, we do choose to go with the younger crowds. Anyone over the age of 30 is typically considered outdated and useless. Unless of course you are visiting one of our spectacular granny sites.
postmodernsideshow.com
Managers look at ages 18 - 25 as people they can abuse. They are inexperienced so they won't stand up for themselves, and usually aren't married so they can work them 60 hours a week for low pay.
Religion is a gateway psychosis. -- Dave Foley
I seriously doubt that people can't learn just as fast at an older age. I'm 46, and think I'm smarter now than when I first starting programming computers in '75. Age also tends to give one experience from which to draw on. The accumulation of previous experience comes in handy at the oddest times, I've observed.
I have no doubt that there are mentally vacuuous hiring individuals who think that younger is better however, and that is a problem. If I encountered that, I think I might send the CEO of the company a paper letter explaining what I heard at my interview, and why I wasn't going to work there.
There are two sides to every coin. I'm a manager of five developers and six support staff.
In my experience, younger people tend to work like dogs until it stops being fun for them. They will pull all nighters all week when you're trying to launch a product, won't need to leave early for soccer and little league games, and won't get in trouble from their non-existant wife for leaving a few minutes late.
On the other hand, older coders tend to work at a more steady pace, have fewer errors, and spend their time thinking about something before they start jamming out code. They also are more reliable at showing up on time, not burning through vacation and sick time the second it becomes available, and following through with their committments.
It isn't really fair what that manager said, but I think they might have experienced some of what I just mentioned above. Although things like that generally aren't to be said "out loud" behind closed doors you'll hear many people talking about things they have observed managing people.
What's the best solution? A balance of both, in my experience. You need an effective mix, an although young people can be great coders and older people can be off sick, those are the general trends I've seen in seven years being a manager.
You have to remember that you are there to solve your employer's problems. If he's looking at someone to produce 1,000 lines of code per hour then you wouldn't be interested in the job anyway. You want to work somewhere focused on quality over quantity, and that is probably more biased to older more experienced developers in many cases than younger folks.
Case
When I was fresh out of college (a little while back) I ran into something related. My boss definitely preferred me for the fact I was youngest and he probably perceived my general energy as also being faster at programming. But I also ran into another problem. Here's an example:
It's a late Friday afternoon and we've got plenty to do, but with plenty of time. The boss tells me he wants the work done for Monday morning instead of the extra week we were originally told we had. The older developers with families told him they weren't staying late Friday, they were going home. I told him the same, but he replies, "Why? You don't have anything better to do." Apparently since I was young and didn't have any family I had no reason not to work more. I was fuming and I didn't work late. He tried to pull that crap a few more times after that.
So not only are younger minds quicker, but apparently they're also easier to manipulate and take advantage of.
Developers: We can use your help.
Senior members are far more respected in the field of law, because it is understood that the older a lawyer gets, the more experience they have; concordantly, the more experience they have, the better a lawyer they are.
What does a lawyer do? Pretty much the same thing as a programmer. A good, experienced lawyer will have a specialty area of law, but be able to learn about new legal arenas as the need arises; likewise, an experienced lawyer will know the ins-and-outs of a specific arena in the legal system, including exceptions and loopholes a younger, less experienced lawyer might miss.
Same goes for programmers. An older programmer, generally speaking, will be more sensitive to over-using resources, will have a better grasp of programming methodologies, and will know about many more former bugs and programming mishaps than a fresh-out-of-college CS grad.
--
I Hit the Karma Cap, and All I Got Was This Lousy
Of course, this behavior could be explained away as economic concerns, as the decision to higher younger (and typically cheaper) employees can directly affect the bottom line.
I am outraged that the widespread discrimination against short folks has taken another, worrying, twist: even in evaluating programming skills!
Sigged!
Why hire young?
Younger IT workers will often put in absurd unpaid overtime, where most older workers won't.
Younger workers just out of college will often take a job at a low salary for the experience. Older workers won't.
Younger workers are often have more exposure to cutting edge tech than older workers who cut their teeth on cobol, jcl and basic.
Younger workers have lower expectations about benefits, perks, salary, etc than older workers who can remember the 'good old days' of 5 years ago.
Older workers are more likely to have children, families, in short lives. Younger workers are more likely to drop everything and fix that server at 3:00 AM.
Older workers have seen many managers pull many tricks, know how to spot them and how to deal with them. Younger workers are generally more pliable.
=brian
I was RIF'd in May 2001 just after the dot-bomb collapse, and was unable to even secure an interview. In the two years that followed, I netted only two interviews although I have over twenty years in programming. I know this had a lot to do with my age, since it was communicated to me through recruiters and other sources that longevity in the field directly translates into dollars. They see that hiring younger necessarilly means hiring cheaper.
Read the paper - it's all in there.
"Stop whining!" - Arnold, as Mr. Kimble
My son and I started taking drum lessons 8 months ago - together. There is no comparison. While he may be more technical and able to do the marching snare roll, etc. I rock all over him on a kit. We both put in the same amount of practice time.
But I love the looks I get from the middle age women as I walk out of the lesson room. Which is probably the root of the problem. Most middle age folks don't think someone their age *should* be learning new skills and definitely not having fun!