Slashdot Mirror


Can Older Software Developers Still Learn New Tricks?

An anonymous reader writes "There's a persistent bias against older programmers in the software development industry, but do the claims against older developers' hold up? A new paper looks at reputation on StackOverflow, and finds that reputation grows as developers get older. Older developers know about a wider variety of technologies. All ages seem to be equally knowledgeable about most recent programming technologies. Two exceptions: older developers have the edge when it comes to iOS and Windows Phone."

19 of 365 comments (clear)

  1. One of two things. by Anonymous Coward · · Score: 5, Interesting

    Older developers are always one of two things. They are invaluable wizards who have tons of experience, adaptability and know all the new technologies, or they are completely burnt out and useless. There is almost no middle ground. There is also a strong correlation between interest and hobbies - if they are doing techie things for fun, they will usually be in the wizard category. If they have just been doing the same old job for decades, and do few tech projects for fun, they will be burnt out.

    1. Re:One of two things. by Medievalist · · Score: 4, Insightful

      It's one of the benefits of experience that you know what to skip... although it's not always the same things for everybody.

    2. Re:One of two things. by pspahn · · Score: 5, Insightful

      There is also a strong correlation between interest and hobbies - if they are doing techie things for fun, they will usually be in the wizard category.

      I can't really disagree here, but I wouldn't say that the correlation be restricted to what is considered a 'tech hobby'.

      I have known a number of men in their upper years that I would classify in the 'wizard' category, yet their hobbies included things like fly fishing, baseball statistics, flying small planes, etc. I would really consider any of these a 'tech hobby', but I would consider them hobbies that require a great deal of technical aptitude to also be a wizard in.

      Keeping the mind sharp is the key. If you do that by observing local caddis fly species, tying your own imitations, nailing the presentation to the fish (including time of day, weather conditions, season, physical stealth), and ultimately landing a 22 inch trout on 7x tippet, I imagine that keeps you just as sharp in the day job than simply doing more day job like things in your free time.

      Hobbies are meant to be hobbies for a reason. If you are an aspiring musician gigging at the local clubs to make your cash and you then spend your free time doing more of the same, but "just for fun", your musical career is probably not going to take you where you'd like it to.

      Completely detaching from concepts related to your occupation/career during your "me time" is absolutely essential to having a long enough career to ever become one of those "wizards". If you're a programmer, and you spend your free time programming for fun, you'll certainly become a solid developer, but there are very few people who love code enough to be able to sustain that for 20 or more years.

      TL;DR - going fishing is better than having a 'tech hobby'.

      --
      Someone flopped a steamer in the gene pool.
    3. Re:One of two things. by gbjbaanb · · Score: 4, Interesting

      or maybe "Wizard" means "the guy who just quietly knows what to do and gets it done", no fuss, no drama, no "ooh we must do a total rewrite in Silverlight".

      When you get to this status, you are a bit burned out - but only by playing office politics with ambitious morons, and playing chase-the-latest-tech-fashion. When you get to this stage you're more interested in making things work instead of just playing with the cool tech toys.

      I know, I used to be a tech guy who did it all in the evenings, and wanted a job where I was just a techie doing pretty much the same... today, I don't give a fig about tech for its own sake, I just care about making the solutions to peoples problems.

    4. Re:One of two things. by geezer+nerd · · Score: 5, Informative

      I took on my last tech job at age 61. I was titled a manager, but as ever before, I could not (would not) keep my hands away from coding. I was in a start-up company involved in a completely different line of work than I had done before. I had learned a lot about XML in my previous job, and in the last one I learned VXML and Perl. And developed my first Eclipse plug-in. My coding experience went back to the old days when every computer architecture was different, there were no "platforms", and all code was developed from scratch. Memory dumps were our friends in the old days.

      I did sense that programming technologies were changing rapidly, and I managed to keep my hand in with all the 20-something coworkers by working very hard to study and learn and apply new things. It can be done.

      Too often, I see folks debating the merits of various languages. During my career I learned a zillion of them. Not a big deal. The big deal is learning the concepts. Sometimes a particular language will embody a concept (such as objects) more clearly or more usefully than another. But once you grasp the concept, the rest is syntax. Once I was searching for a new job and an HR type rejected me because my CV did not show Visual Basic. When I did get a job a few weeks later, one of my first activities was helping a junior programmer develop some Visual Basic code. Although I had never seen Visual Basic code before, I became the "expert" because I could see the ideas and concepts beyond the syntax.

      33, 40 is not "old". I am 70 now, and still get a kick out of reading /.

  2. Yes by cunniff · · Score: 5, Funny

    Now get off my lawn

  3. Old Dogs and New Tricks by the+eric+conspiracy · · Score: 5, Insightful

    If your old dog can't learn any new tricks, the chances are he couldn't learn any tricks when he was young as well.

  4. Older workers cost more. by Anonymous Coward · · Score: 5, Interesting

    They can command higher incomes based on their experience. They are harder to exploit, again because of their experience. Their health insurance costs more (more a product of poorly managed health care policies that are often beyond the employers control).

    Any other excuse for not hiring them is a smokescreen, or worse, an attempt to stigmatize them to drive down the price that their experience can command.

    1. Re:Older workers cost more. by JaredOfEuropa · · Score: 4, Interesting

      This is a crappy argument (or at least, it's only half the picture), but it is the one used often by HR types or those doing the selection. The real question isn't "what does this guy cost", but "what cost/benefit ratio is there". The older, more experienced guy may cost more, but his experience often makes up for that, and if he is capable of coaching your junior devs well, then you got a sweet deal on your hands.

      Perhaps a more important difference between young and old guys: if an old guy does turn out to be sucky, there's little chance of turning him around. With younger guys your chances of turning a mishire into a success are far greater.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    2. Re:Older workers cost more. by Darinbob · · Score: 4, Insightful

      I'm not so sure about the contacts. I have recruiters ask if I know people who are looking for jobs, and to be honest, I never do. The ones I know out of work I also know aren't a fit (hardware guy for a software job, etc). Plus lets face it, I'm a techie, not a social butterfly, I don't keep up the contacts with all my past coworkers.

  5. Trygve would like a word with you... by Anonymous Coward · · Score: 5, Informative

    http://en.m.wikipedia.org/wiki/Trygve_Reenskaug developed MVC when he was 49, and DCI when he was 78.

  6. Nothing to do with age by WillKemp · · Score: 4, Interesting

    That depends on the individual. I've known people in their 20s who were already set in their ways, and people in their 70s who were still open to new ideas. It's got nothing to do with age as such - it's entirely a state of mind. If you keep using your brain to learn new things, there's no reason you shouldn't be as capable of it at 80 as you were at 18 really.

    I'm 55 and i'm studying science at university. I'm having less difficulty than some of my 20-something uni mates. I taught myself PHP, HTML, CSS, and JavaScript, a few years ago, so i could work as a web developer for a while. I taught myself Java in the uni break last year so i could play with developing Android apps.

    If you use it, you don't lose it!

  7. As a 38 year old software developer by composer777 · · Score: 5, Funny

    I can say... wait, what was the question?

    1. Re:As a 38 year old software developer by oodaloop · · Score: 5, Funny

      We were discussing whether or not you approve of my presence on your lawn.

      --
      Tic-Tac-Toe, Global Thermonuclear War, and relationships all have the same winning move.
  8. Re:Of course not by Emperor+Shaddam+IV · · Score: 5, Insightful

    Yeah, this old fart knows Cobol, Assembly, C, C++, Java, a little C# and several other languages. I enjoy when you younger guys come to me for help because you can't read a log file, resolve a memory leak, write a test plan up, or optimize your SQL. :)

  9. It's not about age. by TsuruchiBrian · · Score: 4, Interesting

    The problem is that programming was a rapidly changing field up until a few decades ago.

    It simply wasn't possible to be a good programmer (by today's standards) in the 1970's. You could be a good programmer for the time. Many of those people have kept current with new design methodologies and many haven't. The ones that haven't kept up, continue to think of themselves as badass programmers who know everything, when in reality the world has just passed them by.

    It is not that old people are bad programmers. It is that people who learned how to program before the field of programming really matured tended to have "stone age" tools and didn't always keep up to date. As time passes, the "old programmers" are changing. I am 33. People considered "old" are not even that much older than me. They had a much different experience learning to program. They didn't learn to program in "the wild west" like some of the really old programmers. Many received formal training at universities where they learned a lot of the theory of computing. They also benefited for learning in a time when more was known about how to program in a way that minimizes mistakes and increases scalability, maintainability, etc.

  10. Re:old people have higher Health Care and don't 80 by Tough+Love · · Score: 5, Insightful

    old people have higher Health Care and don't like pulling 80+ weeks.

    Or even 40+ weeks. And don't need to because they tend to do their work more efficiently as opposed to galloping odf enthusiastically in all directions. Ultimately producing stronger, more maintainable code. By way of substantiation, note that the typical European worker at ~37 hours/week is typically as productive as an American or Asian worker supposedly putting in way more hours. The equalizer is, Europeans tend to plan better and waste less time.

    BTW, note that being an older programmer does not obviate the possibility of having a young lover. Far from it. In work or love it's about keeping your stamina up: take care of your eyes and your body. Treasure your enthusiasm for life. Keep your mind active and never stop learning. The rest just falls into place.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  11. Re:Unable or Unwilling or Unmotivated ? by gbjbaanb · · Score: 4, Insightful

    amen. The thing with old guys is that we've seen the fads come and go - did you jump to learn Silverlight, Linq2SQL, etc? Yes, well, fool you. The old dogs take their time to see if a tech is actually any good and worthwhile before going crazy for it - unlike a lot of younger guys who seem to think that if they haven't completed a project they can move to a different tech and then fail to complete that too, but without anyone noticing!

    Its the same with a lot of stuff- .net moves so quickly that no-one really became a true expert in it, as soon as you learned one tech, it was scrapped and a different one with the same name and different version came along - ho hum. The old guys remember when you made things properly first time (or, if a MS dev, waited for version 3 before taking notice of it)

  12. Old Geeks by the+eric+conspiracy · · Score: 4, Interesting

    A faculty advisor mine really loved his work. He never retired, worked until he died at age 93.

    His university tried to force him into retirement, cut his lab space and other wise tried to hassle him. He was 70 at the time.

    In his early 70's he published some work on electrospray mass spectroscopy (ESMS) which was applicable to the analysis of proteins.

    ESMS led directly the development of protease inhibitors and was a key part of the founding of the science of Protenomics.

    That led to his being awarded a share in a Nobel Prize in Chemistry in 2002. He was 85 and by then had moved on to another university with less discriminatory attitudes towards older faculty.