Slashdot Mirror


Why Companies Should Hire Older Developers

Nerval's Lobster writes: Despite legislation making it overtly illegal, ageism persists in the IT industry. If you're 40 or older, you've probably seen cases where younger developers were picked over older ones. At times we're told there's a staffing crisis, that companies need to import more developers via H-1B, but the truth is that outsourcing and downsizing eliminated a subset of viable developers from the market. Those developers, in turn, had to figure out if they wanted to land another job, freelance, or leave the technology industry entirely. But older developers still have a lot to offer, developer David Bolton writes in a new column: They have decades of experience (and specialist knowledge), they have a healthy disregard for office politics (but can still manage, when necessary), they're available, and they're (generally) stable.

14 of 429 comments (clear)

  1. Around the block by Anonymous Coward · · Score: 5, Insightful

    Here's why I advocate for hiring older developers. I'm in my mid-30s now and I've seen it happen so many times. Some kid comes in fresh out of college thinking he or she knows all the answers. They don't. I don't. They are so trigger happy to re-invent the wheel and over engineer everything.

    You know what I've learned after all these years. I may not know "what works", but I sure do know what won't.

    1. Re: Around the block by Anonymous Coward · · Score: 5, Insightful

      This. I've had trouble with know it alls of all ages really, but more with younger people. That's to be expected really. General lack of experience plus sometimes inflated egos plus the perceived need to prove something just leads to that. Good developers listen to reason and take advice. Bad ones leave, and if we're all lucky, they leave the profession.

      Older developers have experience and a general lack of tolerance for nonsense, but sometimes need to understand why doing something different is a good thing. (Though you may want to listen to them when they tell you different isn't really different. Lots of crap people push as new has been done before.) Good ones take advice, and bad ones leave.

      It's almost like developing is a mindset rather than something one gets worse at with time. (Sarcasm of course. Most of us without a bias against younger or older developers know this and have known it for a while now.)

    2. Re:Around the block by radtea · · Score: 5, Insightful

      I may not know "what works", but I sure do know what won't.

      Age is not a great arbiter of such things, but it's still true that without age there are some experiences that are hard to get.

      I remember when "structured programming" was the silver bullet du jour. Then it was OO. Then it was Java (this is hard to believe, but really, Java was touted as the solution to all our ills, and people believed it for a while, rushing out to re-write perfectly good code in Java and frequently ruining it in the process) Today it's FP.

      All of these, except maybe Java, brought some real good to the table. There were a variety of side-trends that never really got off the ground, at least as silver bullets, like 5GLS, whatever they are.

      An older developer has had the opportunity to watch these decade-long trends and make better judgements about the curve of adoption. Will Haskell ever become a mainstream language? Nope, although it'll be used in some niche areas, the way SmallTalk still is. Will FP techniques and ideas filter in to all kinds of other languages? Well, duh. Already happening. Is it worth learning a little Haskell and maybe come category theory? Sure. You can do that even while thinking the claim "apart from the runtime, Haskell is functionally pure" is precisely as impressive as the claim "apart from all the sex I've had, I'm a virgin."

      Not all older developers will get any utility out of their experience. Some become cynical and dismissive. A very, very few retain their naive enthusiasm for the Next Great Thing. But many of them have a nuanced and informed attitude toward new technology that makes them extremely valuable as the technical navigator for teams they're on.

      --
      Blasphemy is a human right. Blasphemophobia kills.
    3. Re: Around the block by Anonymous Coward · · Score: 5, Funny

      What kind of organization is still using messengers to carry internal memos in this day and age, let alone shooting them when they fail to bring positive news? If that's the sort of thing that goes on there, then there are far deeper problems than mere inexperience.

  2. The problem with older developers... by QuietLagoon · · Score: 5, Insightful

    The problem with older developers is that they have too much experience. Or at least, that is what I was told by the HR persons who did not want to interview me when they saw my resume.

    1. Re:The problem with older developers... by jandersen · · Score: 5, Insightful

      The problem with older developers is that they have too much experience. Or at least, that is what I was told by the HR persons who did not want to interview me when they saw my resume.

      Meaning, they are too expensive and are able to look through the incompetence of managers. I suppose it is quite daunting for a mediocre manager to try to dominate a mature engineer, who doesn't fall for his bluster and can't be scared into submission.

    2. Re:The problem with older developers... by hcs_$reboot · · Score: 5, Insightful

      The real problem with people hiring developers is that they often see development as a first step in life, which a preparation for another job having management responsibilities for instance. They don't understand that some people consider development to be a career, like to code, like to learn technical stuff and don't consider changing for management positions. Moreover, a "natural selection" eliminates the worst developers in their 20's who naturally turn to other jobs after a while. Of course, there are still a bunch of incompetent older developers - but thanks to these many years of experience, it is usually much easier to discern the good and the bad from older developers than from beginners.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
  3. no brainer for HR by crgrace · · Score: 5, Informative

    I've been in the technology business for almost 20 years now. In my personal experience, older engineers are much more productive than younger engineers. Younger engineers are much more likely to partake of the "free" dinner offered by the company and work 80 hour weeks. They are also significantly cheaper.

    To HR we (engineers) are a fungible commodity anyway. Of course they go for the younger people. Given that they command lower wages AND work more hours their effective hourly rate is much lower. So it's a no brainer.

    Of course, I would guess from experience (although I have no specific evidence) that older engineers are cheaper in a productivity/dollar sense, but that doesn't even enter the argument in a modern corporation.

    Unless we get into management, we older folks (Lord, is pushing 40 really older now?) are better off in .gov/defense jobs or working for small companies where individual people (may) value our contributions.

  4. Re:Its more complicated by gstoddart · · Score: 5, Insightful

    It's like that old joke about the young and the old bulls ... Hey, let's run down there and fuck one of those cows. No, let's walk down and fuck them all.

    Instead of asking your employees to knock their brains out, read the fucking Mythical Man Month and realize that the death march is an idiotic way to do things which doesn't really work.

    Too many companies are being ran by MBAs who have no understanding of how to build stuff, and think 9 women can have a baby in a month. Or even that 4 women working really long hours can do it in half the time.

    The problem is companies are being ran by short sighted idiots who don't understand the nature of their business.

    --
    Lost at C:>. Found at C.
  5. A little of this, a little of that. by berchca · · Score: 5, Interesting

    I technically qualify as an 'older developer,' though not old enough to embrace the title personally. On several occasions, I've worked with teams (as a contractor) made entirely of 'age-challenged' developers, and I'm always amazed to get kudos for saying things I consider obvious. Obvious, I suppose, because I have the experience the young'un do not, and experience does help.

    While I'm sure that I have all sorts of limitations I'm not aware of, like I probably smell funny or maybe don't know why Euphoria is the most awesome programming language _ever_, or simply can't hold my own on the foosball table, I think that toddler teams should have at least one elder mentor onboard--someone whose been through the ringer a few times--because we do know stuff that you'll only realize you didn't know after we say it, and we tend to be pretty grounded, which helps if you're trying to do things like, I don't know, make money.

    Just don't let us pick the music for the office hi-fi.

  6. Read lord of the flies sometime by iamacat · · Score: 5, Insightful

    Do you want your corporate culture to be like that? Then by all means only hire kids. Any healthy human society needs an age/gender/personality diversity of contributors to thrive. There are certainly brilliant 20 year old programmers, but they don't have practical experience keeping a project or a team alive and working well for a decade. And once they acquire such experience, they will leave your company because it'a not friendly to their needs.

  7. Re:let's be real for a second by rrr00bb5454 · · Score: 5, Informative

    That's a pretty ridiculous statement. My actual experience intuitively says just the opposite. I work at a security company that is largely made of guys who just got out of Israeli SIGINT (their mandatory service). The older guys write kernel code know what C compiles to, and see the vulnerabilities intuitively. The new ones have quite a bit more experience in high level languages, while being almost oblivious to abstraction breakage that leads to security holes. At best, I'd say that the older developers get stuck dealing with older code bases (that are making the money) and tools (because the newer ones can't deal with it anyway). But on security.... Prior to the mid 1990s, everybody in the world seemed to be working on a compiler of some kind. This deep compiler knowledge is the most important part of designing and implementing security against hostile input; ie: LANGSEC.

  8. Re:Its more complicated by Jason+Levine · · Score: 5, Insightful

    they are perceived to not be willing to put in the hours that younger developers will.

    A younger developer will often need 40 hours to write the same code that an older developer will write in 10 hours. The only problem is when management sees TIME_SPENT_CODING as equal to QUALITY_OF_WORK. So they prefer the younger coders who will put in 60 hour weeks over the older coders who do that same work and more in 40 hours and then go to spend time with their families.

    --
    My sci-fi novel, Ghost Thief, is now available from Amazon.com.
  9. Re:Capitalism by gtall · · Score: 5, Insightful

    And if capitalism decrees that workers older than 40 should not be allowed to work any longer, we should salute capitalism because it has achieved optimum performance? Capitalism does a lot of things well, but it does a lot of things poorly as well. It underlies uninsurance companies cherry picking only healthy people, leaving government to pick up the tab on the uninsured and sick leftovers. Them includes many of those over 40 which no longer have jobs.

    Capitalism doesn't do well with pollution, it rewards passing that pollution onto someone else to clean up, probably government. It doesn't do well with global warming where it cannot point the finger quickly enough at those causing the problem since it may not be a problem until 40-50 year after the pollution that causes it, leaving government to figure out what to do.

    Capitalism doesn't do well in funding poor people to go uni so they'll get better jobs since they have precious little capital to secure the loans necessary to go, leaving government to provide those loans in its stead. Capitalism gives us payday loan sharks so the gullible get gulled more often, many of these tend to hold low paying jobs with little education leaving government to pick up the tab.

    See a trend here?