5 ms·
I am in my mid-60s and I don't feel like I have suffered any age bias either at large companies like Google or small startups I have helped. I sort of grew up
by mark_l_watson 11y ago
I am in my mid-60s and I don't feel like I have suffered any age bias either at large companies like Google or small startups I have helped.
I sort of grew up with computers. My older brother and I got a mini version of a mechanical difference engine when I was a kid. When I was about 11 my Dad got me occasional use of a time sharing system, so that planted some desire in my brain for using computers. In high school I took a class at a local university.
It disturbs me to hear younger people talking pessimistically about their future careers. I advise them to keep learning and working on things that are useful and that they enjoy working on.
Edit: I did run into age bias, or at least I think it was: I had done a homework interview assignment and phone interviews for a back end job for Wikipedia and it seemed like they very much liked what I offered. Then, 1 minute into a video conference interview, I was brushed aside. So, I should have said that I have never had on the job age bias.
- mixmastamyk 11y agoI've noticed that whether you are/were interested in management is a factor. Younger managers can imagine hiring older managers, but rarely engineers.
- true_religion 11y agoI wonder why? Is it because there's something potentially odd about hiring someone with more experience (and perhaps thus a much greater skill level) than you when you are both on the same career track? I have never had to do it, but I'd like to think the 60-year old version of me would be much better at my job than I am. Thus, if I hire them, I'd wonder "why am I tech lead? It really should be the other way around".
- tetraodonpuffer 11y ago> when you are both on the same career track I think this is one of the root issues, the perception that management is somehow the natural next set for software developers. Why should that be the case? It'd be like you trained all your life to be the best violin player you can be, then after some years somebody pats you on your shoulders and tells you it's time to start conducting. I am mid-career, and interestingly I had a couple of short stints in management early career, as much as it helped me quite a bit now with team leading duties and in seeing things from the point of view of my manager when we have 1 on 1s, I would never want to be in management as my full time job. Management and software engineering are, or should be, parallel tracks: there is no competition, so a software manager should be as thrilled to be able to hire an experience software developer as a young hospital administrator be excited if they are able to snag a renowned surgeon for their hospital.
- chrisbennet 11y agoThe metaphor I use is race car driver vs. race team owner. Why would I want to stop driving???
- mark_l_watson 11y agoThat is likely true. Except occasionally being a tech lead, I have never been in any management role in my career.
- wheaties 11y agoGuess I'm an outlier. I like people with experience more than not. I respect more older devs than I do younger. The older devs tend to have the best projects on Github. Then again, I don't allow stupid data structures or algorithms questions in interviews. I can pretty much tell someone's experience level by the types of interview questions they ask.
- deleted 11y ago[deleted]
- sridca 11y agoOh, it is Mark Watson! When I first came across your blog (via Clojure stuff) what fascinated me most about you was your sustained passion despite age. It actually gave me further assurance that my current passion for programming need not wither away in later years (contrary to what most people think).
- mark_l_watson 11y agoThanks for the comment!
- dominotw 11y ago>I am in my mid-60s and I don't feel like I have suffered any age bias either at large companies like Google or small startups I have helped. You obviously have ton of expertise and experience to make age a non issue. This is not the case for older people trying to break into programming. Employers often take a chance with younger employee over older ones if all things are equal. That is bias the article is taking about.
- ronyeh 11y agoJust playing devil's advocate, but isn't that a logical approach? If two junior programmers show up on my doorstep, and one is 25 and the other is 55, why wouldn't I go with the 25 year old (all other skills being equal)? If I'm lucky, maybe the young person will want to work with my company for a decade or two, or even more. Would the 55 year old want to work for several decades more? Of course, I am also worried about age bias. I'm curious what will happen if/when I decide to join a company again after age 40.
- TheCowboy 11y agoI always see this argument but find it possibly disingenuous. Given the rates of turnover for programmers, or even non-programmers, I don't see how people can realistically think this. Young programmers have even more incentive to change jobs more frequently. It's easier to let the data speak for itself, from the BLS: the median tenure of workers ages 55 to 64 (10.4 years) was more than three times that of workers ages 25 to 34 years (3.0 years). A larger proportion of older workers than younger workers had 10 years or more of tenure. Among workers ages 60 to 64, 58 percent were employed for at least 10 years with their current employer in January 2014, compared with only 12 percent of those ages 30 to 34.
- achow 11y agoI would go for 55 without second thought. It would be for the ‘wisdom’ and life experiences; ability to take best decisions when no data is present (better intuition due to more life experiences); knowing that the person would be less likely to quit due to impulses; probability of having better intra personal skills; and so on…
- geebee 11y agoFair enough. This is one reason why I tend to use the phrase "age related employment issues" instead of age discrimination or age bias. It's a mouthful, and it certainly includes bias or discrimination, but that doesn't tell the whole story. I actually think the problems here run deep. There are many aspects of the high tech workspace that don't really appeal to a lot of people, especially as they enter middle age (but by no means limited, plenty of young people don't like it either). Ping pong tables, video game consoles, open offices. The office setup is also a factor - I read an article (NYTimes, I think) about a middle aged woman journalist whose company was purchased by a modern tech media company. She lost her private office and worked in a big open room, with back visibility, where her (often much younger) coworkers were able to track her more frequent trips to the bathroom. Funny thing for me, I was disappointed with this culture even when I was young. I majored in literature as well as math (with a cs focus), and I remember when I was younger how drawn I was to movies that kind of glamorized adulthood for me (the party scene in the movie "Manhattan" where the intellectual avant guard banter really appealed to me - I know it was a fantasy, but aren't all aspirations about what you want to grow up, to an extent?). I started working at Sun Micro after grad school, and while I didn't want to be a lawyer or in finance, I envied something about my friends who went into these fields - they were treated as adults. Their getaways were to nice restaurants, our office getaway was at Dave N Busters. It was a letdown. And I'd say that tech culture has double down on this kind of thing since I was a grad student back in the late 90s. Honestly, a lot about tech culture is really very unappealing to people who don't want to live in a permanent state of extended adolescence. I'm willing to take this a little further and say it isn't an accident - I do think that some elements of high tech are vaguely threatened by the notion that programmers and other technical types are actually adults who might prefer to go to dinner and the opera than dave n busters ad laser tag. It's more of a gut feeling, or an intuition, but I do think that this plays a much bigger role in the disinterest a lot of people have in tech - including young tech workers themselves (who, in spite of a few notorious statements, generally are not the source of age discrimination). A lot of people, to quote someone fairly insightful on this issue, actually value propriety, protocol, and privacy, and will look elsewhere for a career if those things are in short supply in high tech. On a brighter note I always felt joelonsoftware addressed this in a very positive way.
- djb_hackernews 11y agoHow much of your career was contracting, if any? Were you an employee of Google? I have heard Google is probably the best of the SV tech giants when it comes to age discrimination, FWIW. I think contracting is a lot different and in that case more experienced consultants are preferred over younger ones where as it is the opposite when it comes to permanent employment. The thing I don't agree with is that we should be expected to keep learning. As if knowing how to design and write software isn't enough for a solid career, we must learn the "newest" programming paradigm, latest js framework, etc. But this gets in to deeper issues of our profession that allows ageism. Edit: Just looked at your website and it looks like you are 100% a contractor... Again, I think they are 2 very different labor markets for contractors and employees.
- marcosdumay 11y ago> The thing I don't agree with is that we should be expected to keep learning. As if knowing how to design and write software isn't enough for a solid career, we must learn the "newest" programming paradigm, latest js framework, etc. Things change, people do discover better ways to work, and not knowing fads does impact one's ability to work in a team. I'm in my mid 30's and I've already seen better sets of technologies appear with order of magnitude improvements twice. And I expect to claim one more time when the current fad of strict but flexible languages get sustainable.
- mark_l_watson 11y agore: "The thing I don't agree with is that we should be expected to keep learning." I believe that in many fields it is important to keep learning, not just in software development. 20 years ago one of the brightest developers I knew made the case that object oriented programming was the 'final paradigm' and that we didn't need any other model for organizing code and data. Now, I would be tempted to say that functional programming is the final paradigm, except I know better than to make predictions. I absolutely agree with you that learning many frameworks is probably not a good use of our time. "Just in time learning" of frameworks is usually good enough but knowing a few programming languages, and occasionally learning a new one makes sense.
- deleted 11y ago[deleted]