But a 40 year old programmer also can do different stuff better than a new graduate. I mostly do financial software and I have to say that while occasionally we have had recent graduates contribute (and contribute a lot) on the whole most of us who do it for a living are older, have kids of our own, and work hard at it. Many of us are self-employed because we don't *want* to work a corporate job. A few are self-employed out of necessity (things like age discrimination).

The thing is, programming knowledge itself only allows you to solve pure programming problems. Solving anything else requires domain knowledge and that increases with age. Additionally, I find that older programmers tend to be better at smelling where context is potentially problematic and slowing down before a big mess is created.

The problem is actually a lack of sense of history. As Harry Spencer said, those who do not understand UNIX are destined to reinvent it badly. Older and wiser programmers who do understand the solutions that have come before are better equipped to solve tomorrow's problems than the just-graduated hot-shots. But the companies don't know that and so they miss out.


In reply to Re^2: How realistic is an extended absence? by einhverfr
in thread How realistic is an extended absence? by ksublondie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.