5 ms·
"He seems to have missed making the point in the title." I think his title was more of a gimmick to catch people's eyes; I think it worked. "I think the perce
by chaostheory 15y ago
"He seems to have missed making the point in the title."
I think his title was more of a gimmick to catch people's eyes; I think it worked.
"I think the perception that 40 year olds are not up to date on technology is laughable"
I strongly feel that this depends on whether the 40 year old likes programming for its own sake, or they feel that it's just part of a 'clock in' and 'clock out' job. It's also very difficult for many programmers that I've known over the years to step outside of the language that they started with, and start learning and heavily using something new. (Maybe it has something to do with aversion to risk and experimentation? For me, the ease in which a programmer can jump from one language to another, is a key test for their longevity in the field.) Of course this also holds for younger programmers; it's just that their skills are fresher and in my limited experience they tend to be more open minded both technically and to things like longer hours.
That said, I've known two programmers in their 50's who could kick any 20 something's ass in any of the latest tech. Sadly in my experience, they are very very rare.
- adrianhoward 15y agoI strongly feel that this depends on whether the 40 year old likes programming for its own sake, or they feel that it's just part of a 'clock in' and 'clock out' job Your right. It is. Then again it's equally true of the 20 year old in my experience. Most people in their forties who are still cutting code have been through three or four "fashionable" languages and have done serious work in all of them. You'll be amazed a the number of fresh faced young folk I interview who just know Java. more open minded ... to things like longer hours Nah. It's just that folk in their forties have figured out that longer hours aren't more productive :-)
- chaostheory 15y ago"Most people in their forties who are still cutting code have been through three or four 'fashionable' languages" I'm not sure where you're located, but in my experience even in Silicon Valley this is very rare. Most of the older engineers are either all about C++ or Java. A few may tinker a little with a new language, but they rarely take a risk to do more serious work with them. Moreover, many of them just transition to managerial positions. This is even more pronounced in less progressive metros like the South Eastern US. I feel that one main reason I've been able (and will continue) to avoid this trap of comfort is because I'm a neophile.
- adrianhoward 15y agoI'm not sure where you're located, but in my experience even in Silicon Valley this is very rare. Most of the older engineers are either all about C++ or Java. My context: I'm UK based, but I know a fair number of US folk. I'm in my forties and most, but obviously not all, of my friends are 30-60. The point I was, somewhat poorly, trying to make is that in my experience it's equally common to find a single language focus with folk in their twenties. Most young developers I encounter only know one language to any level of competence. Lots of people seem to come out of university having used nothing else but Java. Lots of folk who've self-educated seem to only know one of PHP/Ruby/Python/Perl/whatever. People in their twenties seem just as resistant to learning stuff outside of their particular domain as folk in their forties and fifties. The mild advantage that older devs have is that they've seen languages come and go a few times. If you've got a Java developer in their forties or fifties now, then they were definitely using something else before 1996, and probably something else again ten years before that :-)
- chaostheory 15y ago> The point I was, somewhat poorly, trying to make is that in my experience it's equally common to find a single language focus with folk in their twenties. I definitely agree with that. My point is that newer devs tend to know newer languages that are in vogue. Eventually the cycle repeats itself once these 20 somethings get older. I've already seen this happen to most programmers that I personally know with very few exceptions.
- jiggy2011 15y agoThis is very true (I'm UK based too). When I did my CS degree we were taught Java and that was all most people knew. A few also knew PHP because they were interested in webdev or Visual Basic/Pascal because that was what they had done at A Level. I don't think anyone on the course knew functional programming until we did a module in it. This was particularly pronounced when we were given an assignment to do where the tools to be used were not specified but it was to basically build a shopping cart system. Obviously the best tool to use would be either something like PHP or to use Java but with JSP etc. What the majority of the students produced was a AWT/Swing application to control the shopping cart and used the file writing classes (FileOutputWriter etc) to output HTML. Perhaps the difference though is that young developers would expect to be re-taught a bunch of different stuff when they started their first job.
- jlarocco 15y ago"I strongly feel that this depends on whether the 40 year old likes programming for its own sake, or they feel that it's just part of a 'clock in' and 'clock out' job. It's also very difficult for many programmers that I've known over the years to step outside of the language that they started with, and start learning and heavily using something new." I'm not so sure. At one of my previous jobs I worked with a lot of people in their 50s and 60s who were used to assembly language, Jovial (it was an Air Force contract), and Fortran. They couldn't wait to transition to newer stuff because the old languages were so difficult. On the other hand they were all really smart, so maybe you're right.
- chaostheory 15y ago"They couldn't wait to transition to newer stuff because the old languages were so difficult." I think this is just yet another really poor excuse for not learning something new, which further reinforces my point. There's no reason that any of them couldn't learn something new right now and years before. It's not like the middle class can't afford a really powerful computer. They've been affordable ever since the late 80's. You don't even need a powerful computer to program and learn something new. Nor do people have to pay to get access to new languages, and other related dev tools. Plus even the OS is free now. All you need is motivation to make time for it. In their defense, this is a really hard habit to break and what makes it worse is that most people don't realize that they're addicted to one language. As for myself, I'm too addicted to the imperative paradigm even though I get my toes wet with functional from time to time since it's baked in with some of the stuff I use.
- jlarocco 15y agoOkay, maybe I didn't make it clear. The problem isn't that people weren't learning new stuff. Everybody knew the newer languages - how else would they know they wanted to use them? Unfortunately, not everybody can drop everything and re-implement a large system in a trendy new language.
- chaostheory 15y ago