43 ms·
How the Valley treats experienced people
- WalterBright 8y agoSailing the world sounds boring. It's too passive. I'll be working creating new things until they carry me out in a box. I go out on sightseeing trips now and then, and very predictably at about 10 days I'm itching to go home and get back to work. I did go on a 3 day cruise once. By the third day I was bored out of my mind. I tried to get a tour of the engine room but the crew wasn't having any of that. I also annoyed the crew by complaining that they'd changed course to avoid a storm.
- yodsanklai 8y ago> very predictably at about 10 days I'm itching to go home and get back to work. You don't have to be idle while you're traveling. I always spend a few hours "working" when I travel. I find it too tiring to be out all day anyway.
- WalterBright 8y agoI've tried. It doesn't work too well. I'm too used to my big monitor at home, and my build/test farm.
- hawaiianbrah 8y agoThe monitor, okay, but can’t you access your build/test farm remotely?
- mixmastamyk 8y agoInternet is typically spotty, slow, and expensive on cruises. May be an opportunity for improvement.
- WalterBright 8y agoI could, but that means setting up my home LAN for remote access, which comes with all sorts of constantly changing security issues I don't want to spend time on.
- aidos 8y agoMust have been a strange sailboat to have an engine room :-) Sailing the world certainly isn’t a passive activity, especially if you’re sailing around the world. Ocean sailing involves all sorts of skills (and nerves) as you need to nurse a boat around while using your ingenuity to solve the challenges of things breaking that you can’t replace for weeks. You need to prepare all the food (victualling), learn how to sew sails and teach yourself to sleep immediately while tied to a bed healed over sideways because you’re being knocked about in a storm beating into the waves...because you’ll need to be back up top for your shift in 3 hours time. Whatever floats your boat, though :-)
- WalterBright 8y agoI understand that sailing on the ocean is no small feat, but my problem with it is it doesn't actually accomplish anything. I want to do things that matter.
- CPLX 8y agoThis may be jarring to learn but we all enter the world naked, terrified, and alone, and fairly shortly thereafter leave the world the same way. An individual might find meaning from travel, or meditation, or religious adherence, another from creating a family, another by being the greatest bullfighter to ever live, or creating an electronic simulation of violent war, but in none of these examples should anyone be incredibly confident that they have become an authority on which things matter more than others.
- phkahler 8y agoIn the end all we have is our story. Make it a good one.
- mmirate3 8y agoSpoiler alert: nothing can matter to you once you die. (And everyone dies.)
- 8y ago
- keithpeter 8y agoA cruise ship is basically a floating hotel. Depending on the severity of the storm, the crew probably did not want to be dealing with a significant number of sea-sick guests. It used to be possible to take a berth on a cargo ship to/from Liverpool from/to Halifax. The modern equivalent is a ride on a container ship [1]. They will still avoid really bad storms but you are more likely to see some seas around autumn. [1] https://www.telegraph.co.uk/travel/cruises/news/french-freighter-company-passenger-fares-new-york/ https://www.telegraph.co.uk/travel/cruises/news/french-freig...
- lolc 8y agoI did a short container trip and it was great. We did get to see the engine too! As with any ship: Bring lots of books.
- keithpeter 8y agoThanks for commenting. I was looking at one of the European multi-port trips myself.
- lolc 8y agoI did a feeder-ship from Rotterdam. While it was interesting to see the logistics and tight schedules, next time I would skip a run and stay at the destination for more than the day it took them to exchange containers.
- dahdum 8y agoSightseeing is nice, but what gets me excited is learning new skills while traveling. Culinary classes, language lessons, local skilled crafts/activities. I never get bored learning new things.
- mark_l_watson 8y agoI am the opposite. I love to cruise, my wife and I have been on 23, many for long duration. I like to write and getting coffee at 5am, taking a walk around the ship (outside weather permitting), and then a couple of hours working on a book project in the ship library is a great way to start the day and sets me up for exploring a new port later in the day or reading a good book and enjoying the ocean if it is a sea day. Then at night a fine dinner and a good show. A nice life, and it doesn’t have to be all idle time.
- WalterBright 8y agoIf you enjoy it, that's fine for you. Another aspect I didn't enjoy was being a "guest", which means being treated like a retarded person. It's not the crew's fault, they have to do that because they get a lot of guests that sue when the guests do something stupid. But I don't really care for it.
- MentallyRetired 8y ago> I'll be working creating new things until they carry me out in a box. Dilly dilly.
- throwaway98121 8y agoSomeone correct me, but is the article generalizing some one young CEO to represent the entire Silicon Valley? If yes, is that accurate? I’ve come across those types of people in my career. They were cancerous and didn’t last long. I’ve learned to tune out the noise and cut off people like that. Fortunately for me, I’ve never had run ins where these people had power over me. If they did, it’s a shitty company IMO to bring in people like that and I’m better off elsewhere.
- johnchristopher 8y agoThat's basically the conclusion of the article.
- samatman 8y agoThe tech industry has a reputation for being hard on older engineers, and I’m sure there is some of that, but I doubt it’s the problem it’s made out to be. Anectdote, I know, but the older engineers I know are doing fine, one gentleman pushing 70 recently came out of retirement to work on Ethereum. The number of developers has roughly doubled every five years for about thirty years now. Even before you subtract programmers who moved into management or got out entirely, there’s just not going to be that many. This is more for y’all youngsters who are afraid you’ll be put out to pasture when you turn $age-you-think-is-old. No reason to think it’ll happen, experience is useful, you’ll be fine. Yes, you’ll find some ageist managers out there, who won’t hire you if you’ve been legally drinking for more than ten years. Good! You dodged a bullet there, such people invariably have other bad habits.
- AmericanChopper 8y agoShhhh, you’re busting the narrative. But seriously, I’ve worked with some amazing older engineers. I’ve always had great relationships with them, and I’ve learned so much from those kinds of people. In my experience many older engineers are much more chilled out and willing to give their time to help others.
- ddingus 8y agoFlat out, they have experiences. Sharing those matter. Maybe the other person can avoid more bad experiences. I love working where there is a mix of young and old, where they get along.
- yulaow 8y agoSame here. I must say, in my work experience, I had problems only with engineers as young as me (or around my age) who had a big ego, a very bad personality or the I-am-very-smart syndrome. Instead usually the "old" engineers who stick in a tech position were always extremely humble even if having a ton of domain and company-specific knowledge with the willingness to share all of it.
- AmericanChopper 8y ago
- z3t4 8y agoWhen I started programming I was very productive, even more then today, but I was ignorant about performance, data races, xxs, sql injects, lower level programming, sysadmin, general CS, etc. So I think the problem is managers see new guys being more productive, but the old "slow" guys gets paid double.
- Ma8ee 8y agoOf course it is faster to build a solution with bad performance, is hard to maintain and a nightmare to test. The manager who doesn’t know the difference is just a bad manager.
- JustSomeNobody 8y agoI would argue if you were ignorant of those items, you were not very productive. Someone eventually had to come back and fix that. It’s like tossing code at QA that you didn’t debug first. If your initial dev time was 8 hours but you have 6 more in fixing issues you didn’t really get done in 8 hours.
- z3t4 8y agoAs a senior developer you have a dilemma, leave code dept and maybe later get accused of writing crappy code. Or fix all edge cases and and get accused for being too slow and expensive. By the time I have assessed the requirements to chose the optimal balance between hardness and dev-time, setup the right environment and automated the deployment, and made a plan for scaling out ... My former self would have already shipped the code, it would be billed, and the boss would be happy. But you are right about the total productivity, because a year or so later, the boss will wonder why something that took 3 minutes to do before, now takes 3 hours. But usually those hours are billable, so the boss is happy anyway. Then there's time to market vs software quality, how performance and security only becomes an issue after the fact, maybe I'll write a blog post.
- DanielBMarkham 8y agoI took a bunch of time and focused on helping coders instead of coding myself. I came to coding naturally and never thought of it as much more than intellectual self-stimulation. It was a lot of fun, and there is some value to it -- but it tends to get a lot more attention than it should simply because it feels so good to do it well. Successful startup founders say that coding is no more than 2-3% of the total effort of providing value to people. I've found nothing to prove that false; and I've seen a lot of companies and startups. Recently I'm back to focusing more on coding. I find two things most interesting: 1. As I get older, I struggle with attention span and short-term memory more, but I have greater ability to see deep and widespread cross-cutting patterns. It's probably an even trade. 2. I'm not so sure that smart people should be coding. The more I think about it, the more convinced I become that good coding is managing cognitive complexity. You're always trying to make it work, then make it easy to understand and maintain. When I think back on all of the multi-billion-dollars I've seen in project/program disasters, none of it was because the problems were hard. They were all a combination of poor customer/user participation and smart folks taking a problem of n complexity and making it into a problem of n^n complexity. Usually the two were related: tech was constantly used as sort of a band-aid to fix people problems. It never worked, but it kept a lot of coders employed for a long time. Hopefully this wasn't cynical. I love coding and I love making useful things for people. I have a deep passion for helping developers lead happier and more productive lives. But I also feel an obligation to be honest about what happens. It looks a lot different at 50 than it did at 25. Think about it. Seriously, would you want somebody telling you that you wasted three years of dev time and could scrap what you have and roll something useful to production in a month? I've done that several times in my career, at various ages, and nobody ever liked hearing it. As I got older they liked hearing it even less. In this business, inexperience, raw intelligence, and enthusiasm are the things we reward. They come mostly with younger folks. Tech development is amazing and incredible because we create our own realities. But part of that awesomeness is the fact that left alone, we create realities that look like ourselves. It is the nature of the work.
- taneq 8y ago> 2. I'm not so sure that smart people should be coding. It depends on their attitude. The smarter the better, IMO, as long as they understand that the code they're writing isn't for them. They can go hack on some personal project if they want to flex their "I'm so clever" muscles, but if they're writing commercial code, that code is for the dumbest of the dumb who will ever have to maintain it. If someone can focus their intellect towards making their code clear and simple then great. Of course, as you say, someone who's competent but has a slightly humbler intellect will just automatically write simpler code.
- cathames 8y agoLuck is a huge part of success. It's mythology that if you work hard enough for long enough that the world will become your oyster. Sweat and ingenuity are often necessary but not necessarily sufficient means to financial gain. No one launches from the same starting line nor runs along the same track. And don't forget that all the other smart folks out there are ravenously competing against you for those hotly desired greenbacks. Count your blessings if you are one of the lucky ones.
- WalterBright 8y agoIt's not about working hard, and never was. It's about working smart. And people make their own luck. You can't get lucky if you're not in the game swinging. I've known plenty of people who just sat at their desks, doing as little as possible, waiting for the boss to direct them, reading hackernews(!), watching the clock till they could go home. They were never going to get lucky. Then there are the ones who are always up to something. They're doing a side project, they started a band, they go to meetups, they write articles, they talk about their investment strategies, they're planning out their next venture, and you know they're going to get lucky.
- buoyantair 8y agoTrust me no matter how smart you play, if you are born in this world at a very vulnerable position, like say a marginal group like lgbtq communities in third world or in a war torn area or with disabilities, no matter how smart and hard you work, you are always a few clicks behind those who have the "luck" and everything else on their side. The world is super unfair place and sometimes even if you work really smart and hard, you won't get the results you worked for.
- WalterBright 8y agoI'm talking about the US and being an able-bodied adult.
- perfmode 8y ago
- pojzon 8y agoWorks pretty well for Google tho. Too bad most companies dont understand that they are not Google! and never will be - most often - dont even have to be. Unfortunately most managers are sheeps, only able to copy ideas of other ppl without thought if its even needed/required. Im in this industry for a few years and already see that all middle level managers should be fired. Software Craftsmen would be a lot better to lead projects.
- xb10y 8y agoHow does it work for Google? Except for the "search+ads" division, which seems too important to ruin, Google gives the impression of a highly unfocused company with internal feuds and fiefdoms that releases one half-baked product after the next. It seems to me that Google only hires to keep people from working for the competition.
- dannypgh 8y agoI think you might be greatly underestimating the fraction of the company that works on search or ads if you think you can make a meaningful comment about the company that starts with "Except for the 'search+ads' division."
- romeisendcoming 8y agoYou could be right. The security team and some of the kernel developers are top notch though.
- lolc 8y agoYour perspective will grow naturally with your experience. But your attitude will need painful work.
- ramtatatam 8y agoI had a chat with some recruiters recently and they told me there is no future in the industry for people who are 35+ years old. I'm 33 so I just smiled and walked away. I later learned the founder of this recruitment company was 26. Young kids seem to think there is no brains in older people. On the other hand I always thought the natural progression for the programmer is to move to higher abstraction level, become lead/coach/consultant... or start something on their own.
- Swizec 8y agoOlder people discover leverage on time. It doesn’t matter how good you are, a team of 10 well-managed programmers will always out code you. You can hve higher output per hour, if you do the well-managed part. Or you become a teacher. Make 10 programmers 11% better and you’ve contributed more to the company’s bottom line than you ever could on your own. Or a consultant. In that one highly specialized area where you are king ... well a team of 10 can’t touch you because your pattern matching solves the problem right away. Ultimately the older you are the more you understand that hey, maybe if your work is contributing millions to the bottom line, maybe you should be compensated proportionally and that $150k is a joke? This understanding is a problem for new founders. First of all, they’d like to pay you less moneys and give you kool-aid instead. Team spirit and all that. Second of all, you are likely waaaay overqualified for what they actually need. Makes you hard to keep around and engineering churn is one of the toughest things to work around on a product team. Institutional knowledge is king. So ageism comes about. Because experienced people are both expensive and unnecessary.
- qaq 8y agoIf you are 40+ you kinda expected to have a network. We have a dude pushing 70 he would be able to get a new job the day he would let people know he would consider switching a job.
- ghaff 8y ago>If you are 40+ you kinda expected to have a network Every job I've had in computer-related tech since the first one out of school came from people I knew and had worked with.
- avip 8y ago<disclaimer: am old? My kids sure think so> Ageism is real in many verticals. It is healthy to acknowledge that. It’s equally important to face facts related to age: I am noticeably less focusable, and my memory is not as good. I slowly become less fluent in adopting new tech, and it shows (or feels). Most importantly, I have many out of work responsibilities - parents (not getting younger) and kids (not getting older in sufficient pace). Consequently, odds of me doing after hours learning are diminishing. I don’t do open source any more, nor do I have time for cool side projects. And all that, not the invented stuff in OP, is what makes ageism a thing.
- ramtatatam 8y agoWould you share how old are you? Sorry if you find that question out of place, but I'm 33 and have kids and I don't (yet?) make such observations as yours.
- sokoloff 8y agoNot @avip, but I’m 47 and definitely feeling the time/family responsibilities crunch. Our parents have all just turned 70+/-2, we have two smart kids in elementary school who need to be fed almost every single day :), a house/yard instead of apartment, everyone’s healthy, but just managing school, activity, and holiday calendars is grueling. In my 20s and 30s, I could code like hell, have time to devote to learning new thing in depth, and play on 4-5 sports teams. Now, I’m still able to function almost the same mentally, but there are 20-40 fewer “free” hours in the week. Something has to give and we’ve decided it’s not the kids... I wouldn’t go back and change anything, but it’s not the same.
- gaius 8y agothere are 20x-40 fewer “free” hours in the week Giving up Facebook was a huge win for me. People just don't appreciate how much of a time sink it is (by design). You might think "I'll just check it" then you look up and a quarter or a half an hour has passed! For example I have 2x30min train journeys per workday. I used to spend them just idly scrolling the timeline, clicking like, maybe making some comments. Now I use them for reading on Kindle, or doing a module on EdX or Coursera. And that's even before all the other time I would spend on it. I literally got back 5-10 hrs/week, and it boggles my mind that I ever wasted that time to begin with!
- JanneVee 8y agoWell even outside of Silicon Valley the question changes to “why aren’t you a manager yet?”! Annnoying ageist question, despite that my experience is worth the money. You just need to avoid companies that doesn’t value it correctly.
- mr_custard 8y agoMy answer to that question is: "I've tried management and whilst I was told that I was good at it, I didn't enjoy it much - I discovered that I simply enjoy building and creating things, and that's what I do best". Nevertheless, I appreciate that it's an irritating question, but I usually put it down to lack of empathy and/or life experience of the questioner. It would seem that some people just can't imagine that other people have lives, thoughts and aspirations that are different to their own.
- gms 8y agoArticle commits a classic fallacy: one bad example leading to a general statement because the latter makes a better headline. Rather like going from ‘my friend’s house got robbed’ to ‘all houses get robbed’.
- loup-vaillant 8y agoBecause the author related 2 anecdotes din't mean they're the only ones they witnessed. They may have seen a pattern over time.
- neeleshs 8y ago... which should be mentioned with numbers. Otherwise go by what's in the article - 2 anecdotes. My anecdote is that I'm > 40 but highly saught after engineer,by several CEOs far younger than me. But I know it does not mean that's the general pattern. Edit: everything in the article was a good read, except the generalization in its title
- Dowwie 8y agoIf I go to a doctor who misdiagnoses an issue I have, I don't generalize that all doctors are incompetent. That doctor, in my particular case, misdiagnosed my issue.
- intralizee 8y agoI think people prefer this mentality when the economy isn't doing so hot. Same goes for people who think they're being treated unfairly by age. The health of the economy is the deciding factor and depending on the health of the particular industry as well. Older developers I've encountered have always been super. Unless they have some ego that tries to claim superiority by "age" equating to more experience; which is never the case.
- Terretta 8y agoOn a contrarian note: Below a certain age, tooling and practices knowledge is likely to be up-to-date. First thing they learned was today’s ways. Above a certain age, it takes additional expertise to assess whether the individual kept learning every year or just kept relying on the first thing they learned. Recruiters and contentless managers often fail to tell the difference, so mis-bias on age which doesn’t cause but can correlate to out-of-date skills. At both ages, young and old, assess for self-learning, not age.
- loup-vaillant 8y ago> Below a certain age, tooling and practices knowledge is likely to be up-to-date. There are exceptions. C++ game devs for instance often shun the STL for good reasons (compilation times, performance of debug build…), and then the junior fresh from college must unlearn most of what they believed about "modern" C++. They're up to date on the standard all right, they're just not up to date on the best practices of the field they're getting into.
- zrobotics 8y agoSlightly OT, but hasn't this changed in recent years? I'm not in the industry, but I'd heard that things like EA_STL had gone out of fashion in favor of just using STL. If this is the case, are there any resources for what to be wary of in the STL?
- specialist 8y ago1/ Keeping up involves unlearning too. For me, that's the hardest part. Trying to approach everything with a "new mind". Meaning my expectations for how stuff is supposed to work gets in the way of seeing whatever is in front of me for what it truly is. 2/ A fair amount of new stuff isn't better. Or it's a mixed bag. Discerning the Brownian motion from the legit improvements is a lot of work.
- ghaff 8y agoI've long found that there's a fine line between legitimately noting that the last 8 incarnations of $CONCEPT didn't work for A, B, and C reasons so #9 isn't likely to fare any better and being endlessly negative about every new idea that comes down the road because almost every new idea is an echo of a prior pattern at some level.
- shmat 8y agoSometimes you don't make enough money to retire early from a combination of bad luck and poor financial decisions. In my career, I followed a pattern of going to a company just a bit too late to get the really low priced options. I've ended up with dozens of former co-workers who are multimillionaires. I had a family and was (in hindsight) too conservative about when I went to a company. I also was a "paper" millionaire during the dot-com boom. The start-up where I worked was bought making my options worth millions. There was a 6 month lock out and during that time the stock price went from $75 to $0.75. My options were at $2. Did that make me a bad developer? At another company I had options at $7. The stock peaked a few years later at $60. I never exercised any because I was greedy. I was going to cash out when it hit $75. When I left the company after 6 years, the stock was at $8. All in all, I was almost always one of the best developers, but I never made "FU" money. I did learn to exercise options as soon as they were worth a decent amount, but never made enough to be rich that way. I'm sure there are many old developers who were as dumb financially as I was.
- leemailll 8y agoThat sounds quite unfortunate for your stock options. But why don't you sell your options, pocket it, and set up an investment portfolio to reduce risk after the first crash?
- happythought 8y agoOp admitted to being unwise financially, so your comment kind of seems like rubbing salt in the wound.
- xuki 8y agoDon't beat yourself up, hindsight is 20/20.
- shmat 8y agoThe only one I beat myself up over is hanging on to options too long, since that was greed. The other decisions were all reasonable given what I knew at the time.
- mark_l_watson 8y agoI am 67, but this story occurred when I was young and just out of college: there was a very old computer programmer at work who had great skill but he miss-applied it. The worse thing he did was writing tortured FORTRAN code that self modified itself at runtime - hardware architecture and operating system dependent binary patches. I promised myself I would never be that guy, read the book ‘The Egoless Programmer’ and followed a different career path from my old friend.
- diego_moita 8y agoYou touched a different but very important issue: in this industry you need to recycle yourself, you need to stay up to date with new technologies that overcome the old ones. Being old doesn't necessarily means being obsolete, but you need to deliberately avoid obsolescence. Sometimes the new shiny things are actually good. Some technologies fade and you should avoid fading with them. Assembly programming has become a niche for people that write compilers. FORTRAN is giving space to R and Python. Very few people still write COBOL.
- alanning 8y agoI wonder if part of the issue is a kind of unspoken fear that the “dream” outcome may not be as common as people want to believe. If I am a young developer with more stock options than salary I want to believe that I will have the option of retiring early. Seeing older devs who were not able to “cash out” plays poorly with that narrative.
- molson8472 8y agoNailed it.
- bartread 8y agoMy team has five middle-aged guys[1] on it, myself included, out of a total of 9. Three of the other four were hired by me. I can only live in hope that next time I need a job I'll be able to find somewhere that values experience as much as we do[2]. [1] It's changing slowly but female software engineers are very much in the minority in Cambridge. I suspect, although cannot prove, that the skew is even more pronounced amongst those of us in our 40s and beyond. [2] Also, we're still hiring.
- wildmindwriting 8y agoI have noticed the female SWE are in the minority in the Boston/Cambridge area, too. At my first company in Boston, I was the first and only female programmer for a good year and it wasn't for lack of trying to hire more. I don't remember another female programmer on the web side (there were quite a few on the hardware side) but most of the team was over 30, with family, and was a good range of ages. Now, I manage a team of five developers, only one of which is another woman. I'm 40 and she is 64. Then again, the youngest person on my team is 35 so we don't seem to have the problem of ageism in our company, thankfully. When we were looking for extra help, it was very difficult to even get people in to interview, let alone someone experienced enough. I'm hoping the job market for tech continues when I need a job again!
- arconis987 8y agoI’m so grateful to have worked with older colleagues who did not care about using the framework du jour. Influenced by their experience, we made some unorthodox tech choices as a web startup, including the choice to use C++ and Lisp-like languages heavily, and it worked out beautifully. From them, I learned that it is more important to ship simple, fast code than to contort your system to use the latest tech fads when it doesn’t make sense.
- mcguire 8y agoIt's always entertaining when you do the simplest thing that works, it works, and then you get to watch someone struggling for months to replace it because it was too simple and not buzzwordy enough.
- pdimitar 8y agoI am not gonna be ashamed to admit that working like your parent commenter said is a good way to ensure you won't get fired out of the blue as well (since what you created is not easily upgradeable or replaceable). But in any case that's a side effect of being competent and is not a specially crafted tactic -- at least during my career. And finally, we have to fight hard against the philosophy that all programmers should be easily replaceable cogs in the big machine. That's an impossible dream of the businessmen but they still won't give up on it.
- slics 8y agoIf one thinks 35+ is to old to code, well I have news for you. At 35+ you learn how to manage time and prioritize better. Life throws another ranch in your bucket of problems, marriage and children. When you are young, you are hired as an engineer to work 40 hours, which we all know very well that working for startups that means 80 hours or you are not putting good effort. Well with a family that’s not possible, as you know that 40 hours at work means that exactly. The rest of the 40 hours are meant to be spent taking care of your family. So if one more recruiter doesnt offer the job interview, it’s because they don’t understand what life is all about. If you have no time to socialize and network or raise a good family, soon we will be left with a society that only focuses on how to better themselves and not mentoring or preparing the next generation of smart people. Talent is not born, talent is made and it starts with a good foundation, called FAMILY.
- zaptheimpaler 8y agoUnfortunately these kinds of shitty recruiters and companies will always be around - none of them are thinking about lofty societal goods like family or what happens 40 years later, they are thinking about how to get the most work for the lowest price for their company. As long as droves of young people continue to flock to tech to try and get their share of the money, hiring is a buyers market. Throwing out old people or young people who dare to demand work-life balance will remain a viable strategy for the buyers and many will do just that.
- j45 8y agoIf there's fewer kids born today, there's a likelihood of fewer coders in 20 years.
- zaptheimpaler 8y agoOn the other hand, 1 person who knows AWS well today can do things that would take huge capital investments and a team of 40 people 20 years ago
- 8y ago
- taude 8y agoLiving and working in the Boston tech market, I have a lot of thoughts about Ageism. It's very much alive and well here. There's also a severe case of Elitism if you didn't go to MIT or Harvard, too. I'd like to think more about this and write dome some elegant thoughts, but... I'll sum it up as it's a little humbling but massively humiliating. It's extremely frustrated being interviewed by people with obviously way less experience and people applying their hiring "playbook" without much thought. I'm pretty sure many companies hiring is explicitly catered to aging people out, or at least setting a different bar for older engineers. Also, when I do get a job offer it's for quite a bit lower salary that much younger, less experienced people who are two or three years out of school are making in this market. It's almost as if the tech industry wants most of the people to have two or three years experience. I've been equating it to working in Hollywood to some. Still trying to figure out where I went wrong in my career, but as others have said below, not all startups you work for succeed, not all companies you create succeed, lock-up periods, senior executive corruption (I worked for a publicly traded company where the CFO actually went to jail), etc.
- sokoloff 8y ago> I'm pretty sure many companies hiring is explicitly catered to aging people out, or at least setting a different bar for older engineers. > Also, when I do get a job offer it's for quite a bit lower salary that much younger, less experienced people who are two or three years out of school are making in this market. Which is it? Do you want an older engineer to have the same hiring bar and same compensation or a higher bar and higher compensation? Realistically, there should be no "same bar, but higher compensation" option. If I'm paying you more, it's because you're better, not because you have more candles on your birthday cake.
- mcguire 8y ago"Higher bar, paying less" seems a strange choice, though.
- sokoloff 8y agoMy experience on the hiring manager side suggests that when that happens, what's usually going on is that the experienced dev failed to meet the higher (level 3) bar but seemed like they'd be a solid individual contributor at level 2, and therefore received a SWE2/PR2/Foo2 offer. In other words, "same [lower than they expected] bar, same [lower than they expected] salary" as someone 2-3 years in industry.
- chasing 8y agoYoung developers will work mindless hours and not demand proper compensation. That's why (poorly run) start-ups prefer 'em. Also, wealth is the world's shittiest metric for success. I know a ton of people with incredible skills who work rather low-paying jobs because they want to improve the world, follow a particular passion, or whatever.
- enraged_camel 8y ago>>Young developers will work mindless hours and not demand proper compensation. That's why (poorly run) start-ups prefer 'em. Well, there are other reasons. People you hire straight out of college tend to feel grateful, and also feel like they need to prove themselves (which is true). So they are usually willing to work extra hard. This can be a good quality, if nurtured properly with guidance and training.
- chasing 8y agoTrue. I was being a little flip, there. There are also jobs that would be a waste of time or dreadfully boring for senior devs to spend their time on.
- opportune 8y agoI think I must be one of the younger people on this site because while I agree ageism is a bad thing in the sense that age should simply not be a factor when it comes to hiring/pay, and that experience is good, I also have direct experience working with older developers who didn’t know the new tools we were trying to use (in my case, AI and big data) very well and so weren’t any more productive / were less productive than younger people who were more experienced within that subject area. That being said, by far the best engineers I’ve met were the people who usually pioneered these systems 20 years ago and were now domain experts. But what I mean by this post is that I also have met a bunch of people who basically only know basic crud, and just because they had a lot of experience in that area didn’t mean that transferred very well to other areas. There’s a limit to how much your knowledge of SQL and Windows server from a decade ago will help you with Kafka and Cassandra
- zrobotics 8y agoBut that has nothing to do with age, and everything to do with poor skills-fit. Because someone fresh out of a CS program won't be all that much better. You admitted that there are cases where experience helps, but some team members don't have that experience. Isolate for variables, don't compare apples to oranges. You are comparing older engineers without relevant experience to "younger people who were more experienced within that subject area." What about younger engineers who aren't experienced? I suspect their performance will be equally poor, if not worse.
- AnIdiotOnTheNet 8y agoThe value of older, more experienced workers is the wisdom they've accrued over the years. There's a reason they don't jump into every new fad that comes along and stick with tools that they know work.
- romeisendcoming 8y agoThere is a limit on where kafka and cassandra are best solutions for your domain. Anyone who only knows SQL and windows server shouldn't be working on new technology stacks.
- rb808 8y agoIs it really common to retire at 35? I'd think it would be just a few could afford that. Around here property taxes plus health insurance for a family is $50k/yr. So from 35->65 that is $1.5m. Not including cost of living of course. Maybe the stock market has been way too successful in the last few decades. Ask a European or Japanese person about retiring early and living off the market. (of course many 35 year olds are struggling to save for a house deposit let alone thinking about retiring)
- gedy 8y agoYeah I only hear that from 20 somethings who extrapolate their 401k and salary from past 3-4 years of good gains. It's all they've known. I used to think that way, but after the two big downturns in 2001 and 2008 I am sadly a lot more realistic now..
- joejerryronnie 8y agoNo, it is not common - even in the mythical valley. Very few people relative to the entire industry strike it rich with enough money to travel the world drinking champagne and eating caviar. The typical valley story goes: When you're 20 - Live in SF and chase your startup dream of making it big. Most likely left with a bunch of worthless options and too little pay for the hours you worked, but great friends and memories (mostly of the after hours parties). When you're 30 - Transition to FAANG like company. Live in SF and commute to the valley. Start making some real money but feel like you sold out. Still harbor dreams of quitting and launching your startup - right after that next big vesting period. When you're 40 - Screw startups, you've got a family to feed, a mortgage to pay, and college tuition to think about. You've finally made the move from super-hipster, urban, walkable SF to a random suburb in the valley and may have even purchased gasp a minivan! Secretly, you find it a much more pleasurable living experience than SF but won't admit that to anyone. When you're 50 - Hopefully, through hard work, smart financial decisions, and a little risk taking, you've gotten your finances under control. You've figured out how to use debt effectively, have a solid set of investments, and ideally are working toward multiple streams of income. You can now legitimately plan your next big career progression, whether that's retirement (still several years out), scaling back your full time work to focus on passion projects, or actually launching that startup (with a statistically much higher probability of success than any 20-something founder).
- EliRivers 8y agoOn the general theme, as I type I have a gap in my team that on paper is for a more junior, inexperienced developer; I have deliberately not starting looking for someone to fill that post, and told HR to consider it simply frozen for the moment, because right now I simply don't have the spare capacity within the team to take on an inexperienced developer. Another vacancy, for a more experienced developer, I am hiring for.
- 11thEarlOfMar 8y agoAverage age on my engineering team is about 55. Until recently, the eldest was still coding at 73. When I look across the team, the more productive ones are those who keep their skills and tools up to date. Find a 30 year vet who can code the same routine in both Go and Python and you'll usually find a productive, dependable engineer who steers you around many gopher holes.
- gdubs 8y agoYoung Michael Jordan could leap high and perform dazzling feats in mid-air. Old Michael Jordan had tired legs, but could destroy the competition with an insanely tight post-up game, and a virtually undefeatable fade-away jump shot. I’ve personally always felt incredibly fortunate to get to work with people who’ve been in the industry a long time; you can learn a lot from them. And while you sometimes can get a “step” on them with your youth, they’ll often school you with the fundamentals. This is part of the diversity conversation — having a team composed of people from all walks of life is a competitive advantage. But it takes an enlightened “coach” to see it.
- yegle 8y agoPretty sure the CEO mentioned at the beginning of the article was referring to Mark Zuckerberg's "young people are just smarter" comment.
- mcguire 8y agoI dunno. Maybe it's because I was just sitting here reading Ian Stewart's chapter on Sally Clark and pondering probability, but I rather suspect that the probability that you're over 50 and suck is much higher than the probability that you are over 50 and are a badass. Mostly because the probability that you suck is incredibly high. And I'm saying this as someone who is over 50, with a phd, a bunch of programming languages and blog posts, and crap on GitHub. And I know I suck. Hell, the primary advantage I have over most of the people I've worked with is that I know what a badass looks like in the wild. I think I'm going to get some more coffee now.
- jrowley 8y agoI think your definition of suck is different than that of the authors.
- zrobotics 8y agoI would agree with you that likely the majority of people over 50 do 'suck'. But... so do the majority of people under 50. Somehow, things still get built and projects get finished. Fetishizing the rare genius doesn't help anyone, since by definition they are a rarity. How, exactly, does age make for worse employees? Since this discussion is about ageism specifically, and not that 90% of everything is crap.
- romeisendcoming 8y agoThere are a couple problems with your post coming from a 50+ year old. * Statistics and probability. * PHD,blog posts, > 2 PL and github in the wild = respectable technical resume. * Badass is as badass does. I work with CS PHDs who are great with math->algo mappings, pattern recognition and data structures that couldn't build a scalable system in fifteen years. Instead you'd end up with some cloud struck monstrosity. I worked with ex auto mechanics who were so quick and deft with hardware, components and diagnostics that they could run/build a DC by themselves. Which is the badass?
- fourthark 8y agoYou never outgrow impostor syndrome! Hang in there, friend. Your coworkers probably don't think you suck.
- gizmodo59 8y agoAgeism is a real factor in tech companies but as the demand grows and tech companies have been around for decades this might go down a bit. May be not for startups but FAANGs definitely will have more aged developers. It’s also important to realize the other factors play in this. Where you are born, your race matters a lot more than many people think. Two people of same age and equal talent but different race aren’t treated the same way in almost any country in the world (Not trying to generalize but it is prevalent)
- withhighprod 8y agoOff topic, such Social Darwinism is in huge favor around China’s tech industry.
- jacquesm 8y agoIf you're doing the same thing for 30+ years you probably are doing something wrong anyway unless it happens to be the thing that you enjoy doing most.
- pdimitar 8y agoBrain craves diversity. That's a fact. I love programming a lot even at 38 but lately I really feel the need to immerse myself into something else for a while -- and I am pretty sure I'll come back to programming even stronger and smarter. I just need to get programming out of my head for a few months. ...But living paycheck to paycheck robs us of the opportunity to give in to this very human need (diversification of our experiences). This has become one of the reasons I started to feel old and tired (while still being only 38) and lately I'm putting a lot of conscious effort to be financially wise so I can buy myself a few years of break eventually. That, or I'll improve my self-confidence and work as a consultant and a founder. Time will tell. Did you have such a period in your life? If so, how did you handle it?
- jacquesm 8y ago> Did you have such a period in your life? Yes, quite a few in fact. It has led me to the point where I purposefully shake things up every couple of years to avoid getting stuck in a rut. It took me a decade or two to realize this was causing me problems, but once it became deliberate it actually helped to provide structure. Easily bored is a complete understatement. > If so, how did you handle it? I try to do something radically different every couple of years now. The last company I started has upset my careful plans though, it took more than a decade to take off.
- kannanvijayan 8y agoThis is something that has been bothering me somewhat. The following in particular bothers me a lot: > "Why are you still working?" The answer for me is simple - because I want to. I learned how to program at the tender age of 10 using a book that came with a C64 that my dad got for free from a garage sale. Since those first years, the field at every turn has provided me with new intellectual challenges and as I've progressed I've accumulated different ideas and projects that I'd like to complete. That includes reasonably fleshed out ideas in bioinformatics, in distributed operating systems, in models for runtime type inference for dynamically typed programming languages, virtual machine construction techniques, and more. I will never have enough time in my life to fully explore all of these - each of them will take years of dedicated effort to actually make something out of - so I have to pick and choose wisely to pursue the projects I care about given the opportunities presented to me. My version of "cashing out" is basically sticking my money in a savings account and getting back to working on interesting things.. or if I have enough of it, using that money to pay some people to help me explore some of the more interesting things I have in my mental back pocket. Some of us actually are passionate about our work. I suppose there are many that are in the field simply to make some big money and get out and live "the good life". I consider the life I would live doing that, and it just feels so soul-crushingly boring and insipid. What a waste of a life.
- pdimitar 8y agoWhile I fully agree with your sentiments for the programming work -- I learned at 12 and never suffered a loss of enthusiasm, and I am 38 now -- I disagree on the money part. You can love your job AND be rich. I've seen programmers achieve it. But to be brutally honest to all sides, it doesn't come to you by a mere technical talent. Knowing people, psychology, some sociology and basically having an eye for opportunity seem to be key. I am not rich. I've made a ton of bad financial decisions in my life and for a year now I work really hard to prioritize things properly. I have success on that front and I am now a pretty wise spender (without being frugal, too) but I still live paycheck to paycheck. To go outside that bubble we really have to stop believing in a "secure income". Many investors and financiers say: "diversify your portfolio". We must all be working on 4-5 places with 5-10h a week each I guess? Or just be consultants at several places where the workload for us is low? Have 10 small SaaS businesses each netting us $500 a month? Not sure yet. But I definitely do agree that spending the rest of your life only managing your finances is boring and insipid and is a waste of life indeed.
- matte_black 8y agoSoon I’ll be on the wrong side of 30 and part of the reason I strive to master important skills is because I know I’ll be put out to pasture some day if I can’t demonstrate my value. I don’t want to depend on a post-ageist society to save me.
- strken 8y agoIn my past two jobs, I've found that the software engineers who want to still be software engineers in a decade are in the minority - maybe a third of the workforce. If you spent your early career wanting to become a manager ASAP, then maybe it's easy to slip up and think of older software engineers as people who failed to make that transition, rather than dedicated individuals.
- throw2016 8y agoIt's pretty silly for commentators here to not recognize their current thinking rules their future selves out from any respectable employment and existence in the field because of the prejudice and massive assumptions about others their current selves hold. 1 or lets say even 10 out of 100 will strike it lucky, what are the 90 going to do. Retire at 35? This is exactly like the 'temporarily embarrassed working class' supporting policies against their interests as they expect to be in exploiter roles 'soon'. This kind of ideology tries to reframe software engineering not as a profession like others but some kind track and field with olympic stars dependent on youth working 100hr weeks to the exclusion of everything else. What happens to the majority for whom this does not pay off? This is self importance taken to delusion. This attitude will not only undermine your experience as you age but also directly reduce the quality of people entering the field as anyone studying now with options cannot logically choose a field where you are expected to work like a dog for long odds where experience does not count. You reap what you sow.
- bborud 8y agoIf you have a young CEO with very little prior work experience, why would you expect them to understand how to recruit, hire and manage people who are different from them? We tend to prefer people we can understand and relate to and if you are a 20-something who hasn't had a professional career yet, people older than you may be a bit of a mystery. As will being a CEO or a manager.
- lisper 8y agoI'm one of those people who doesn't have to work, but I do because I enjoy it. I moved to the silicon valley nine years ago, and in that time I've done half a dozen or so job interviews. I got no offers, so now I run my own company. It was different story each time, but the upshot (IMHO) is that the interview process seemed to assume that I was a fresh-out undergrad. In one case, they asked me to debug some Ruby code despite the fact that I told them well in advance that I have never worked with Ruby. There was one notable exception, and that was my experience with Triplebyte. They have a much better technical interview process than any I have seen anywhere else. There is really only one way to assess someone's ability to write code, and that is to have them write code in a language and environment with which they are already familiar. Modern coding is so complex and requires so much infrastructure that productivity hinges as much or more on the impedance match between a person and their environment as it does on their actual abilities. Even the most brilliant coder will stumble if they use emacs day to day and you force them to use vi. If you want to assess my ability to come up to speed on a new environment, I have a solution for that too: hire me as a contractor and give me a week or two to do a real project for you. I really don't understand why more companies don't do that.
- edoceo 8y agoYeah, gig to hire works great for my small tech company.
- greglindahl 8y agoGig to hire doesn't work if the job market is hot enough that potential employees have full-time job offers in addition to your gig-to-hire offer. I've been able to gig-to-hire for offshore developers, but never for onshore.
- edoceo 8y agoGot my most recent two employees this way, one sales, one dev, both had prior employment, I'm in Seattle
- raptordamus 8y agoI saw people quoting Charlie Munger. Munger has done extensive study on the topic of incentives. If you want to know why Silicon Valley is so discriminating towards experienced people you should ask what their incentives are. Startups are incentivized to hire the cheapest, youngest, most naive engineers possible, work them as hard as possible then flip them. If you are old you are no longer cheap or naive. If you aren’t naive, you are unlikely to work 80 hours a week. You can no longer be flipped. Silicon Valley startups want Ivy League type executives. Why? Because the investors trust them more. Humans give money to people who resemble themselves. Ivy League VC give money to Ivy League executives. Joining a startup has a very low probability of making you rich. In fact, they are specifically designed not to make you rich as an engineer. To make matters worse, you have to spend 3-5 years of life you will never get back trying to get the lottery payout. You getting rich as a non founder at a startup means the executives and venture capitalists miscalculated something. Why would they pay you a cent more than they need to? There are plenty of people in the valley who will now work for just their base salary and nothing more. Why should they give you a single dime more than this? If you are a typical high functioning aspergers engineer, you are better off using your skills to become a quant or a trader in the finance industry. Teach yourself. The tools have advanced to a point where anyone can access huge amounts of leverage. I was an engineer for a long time and I realized that all sides of this is a losing game. All I want is to be left alone and financially independent. Big companies are just as bad, except they don’t pretend there is a chance you will get rich.
- pdimitar 8y agoPardon the esoteric language, but I feel almost as if this was written by my future self. > I was an engineer for a long time and I realized that all sides of this is a losing game. All I want is to be left alone and financially independent. ^ This pierced my heart very painfully. Describes my current mindset perfectly. I realized the full extent of how screwed we the engineers are in the job market just a year or so ago. We can bring millions in value but are paid much less than people who basically only bark orders (good managers do much more... but are so incredibly rare). The whole economy of today's world seems to be in favor of certain traits and most of them are luck or incidental -- race, family, area of birth, and most of all: network/friends! I've known people dumb as bricks who couldn't solve a problem if the solution was biting them on the nose yet they knew a few influential people and right now are making ~$90k a month for wearing suits and showing up to meaningless meetings 4 times a month. --- It's not easy starting to come to grips with the extremely rigged nature of the world's economy and NOT be bitter or self-loathing. Not hating myself for being stupid before and not looking objectively at the world is taking 99% of my free energy but I'll keep fighting that battle until I forgive myself and start looking forward to the future. Meditation and exercise do help. Sorry for the personal aside. Your message resonated with me. I am currently 38 years old and just finished an extremely tough and terrible period during which I couldn't get a job even though I aced most interviews up until the last phase when the mythical "poor cultural fit" door got slammed in my face. This happened about 20 times over 6 months. Now, even though I found the perfect company and team whom I very much like, I am left with a ton of existential questions which I don't have the answer to. What advice could you give me? (I'll look into the quantative analyst in more depth for sure.)
- jondubois 8y agoIn my 20s, I used to think like that because that's what I was told by everyone around me. Now I find this idea infuriating. I'm almost 30 now and I've been working insanely hard since before I left school and during university; I've been working at least 70 hours per week for 12 years (40 hours on my startup or corporate contracting day job, 30 hours on a side project). I've had some minor successes but still no big break - I'm not far from where I left off financially. One of the many companies I worked for is doing relatively well and I'm hopeful that my small stake will be worth enough to buy a modest house/apartment someday but it's still a big gamble at this stage; the shares could still become worthless... Even if everything goes perfectly well, it's still not enough for me to retire. I feel that I got very lucky with that one. I can clearly see how it's possible to get to 50 years old working nonstop like a freak and making all the right decisions and still not make it financially. I've been quite strategic about my career so far. I worked for startups which had relatively low valuations, proven tech, value-creating areas, fast growth, good investors, smart founders, were just starting to onboard big clients and sign big contracts. I also worked for a few hyped SV startups too (I worked for a SV-based Y Combinator company for over a year). Even among the 12 or so software companies that I worked at and left, none of them had successful exits yet or grew sufficiently that it would have allowed me to make enough money to retire (even if I could pick the best one and assume that I had been able to negotiate a good equity package). Only one startup I worked at is doing relatively well and that's also the one which I stayed at the longest and have the most equity in. I feel that people who got a big break before they turned 30 missed out on learning about reality.
- slow_donkey 8y agoIf you're optimizing for money, early startups would be the last place I'd look. I'm well aware that I'm making ~60% of a big 4 salary (tc) assuming my options are useless. Additionally I doubt I'm learning as much technically than if I were to work at a big 4and be exposed to much smarter people. The benefits of startups tend to incur huge tradeoffs.
- TagAsDelusion 8y agoevil people in charge
- xivzgrev 8y agoIf accumulating money is important to you there’s basically two ways to match this manager’s expectation: 1) work at Facebook/google/Microsoft/Amazon/etc for X years, keep your spending low, and invest the rest wisely 2) work at startup X for 5-10 years and cash out in IPO A manager can easily see on your resume if number 1 applies. In which case we look at number 2. The odds are good that no matter your badassery, you WON’T hit the jackpot, because a company’s IPO likelihood is dependent on far more things than your contribution. What you see is some circuitous logic - “a talented person has made enough to retire”. But how do you define talented? By the fact they are of a certain age and have made enough to retire.
- S_A_P 8y agoA few questions about this article. 1) is this hyperbole or is it a generalization that seems to follow the 80/20 rule? 2) I can’t imagine that there are enough jobs in SV that could consistently churn out millionaires- right? I would think that maybe some fraction of 1% of the people there hit the start up lotto. 3) I’m guessing this article mentioned here was scrubbed from the internet, but I would be curious to read it. 4) I enjoy working most of the time. Sure there are crappy days but I don’t think I would live a healthy lifestyle were I to be well enough off to not work at age 50. 5) if SV is really generally like this, why would someone want to be there? Is it just to get a shot at launching the next billion dollar company?
- cheez 8y agoI think the truth is that older, more experienced people do not provide visible value. For example, do you think it's undergraduates who come up with the design and architecture for AWS? No, it's years of pain and lessons that go into it. Then the elders productize their pain and lessons so that undergrads never need to learn it. This is why FAANG want undergrads: their processes keep noobs from making super stupid mistakes, through the law of large numbers, some survive, feel some pain, learn and make it to architect level enough to affect the next iteration of AWS/Google/Azure. At the same time, the company saves on salaries/benefits/work-life balance. It won't change because it works. Act accordingly.
- freyir 8y agoIt’s a bit scary to hear these stories, especially as I squandered 20s getting a PhD, and most of my 30s living paycheck-to-paycheck at a non-FAANG R&D lab that pays peanuts. I’d love to move to a better-paying company, but it feels almost hopeless when I walk into a SV tech office and I’m the oldest-looking person there in my 30s. That said, I’ve been interviewing developers over the last few months, and it’s hard to find good older developers on the SV job market (especially at a non-FAANG R&D lab that pays peanuts). We mostly get new college grads who are completely inept. I’d like to think the good older devs are gainfully employed somewhere.
- austincheney 8y agoAll I can say is thank god I don’t work in the valley. Some people actually enjoy programming and don’t have equity. Not everybody who programs is a high school drop out entering the ground floor some trendy ad-based social start up. Some of us actually solve real problems. EDIT: If I had to guess at the quote the article author was looking for I would guess it is this: https://www.cnet.com/news/say-what-young-people-are-just-smarter/ https://www.cnet.com/news/say-what-young-people-are-just-sma...
- drharby 8y agoThe article referenced on this one, regarding company culture, is spot on for my current role and company. But the author's observation of 'make hay while the sun is out ' is spot on. Shame on company middle managers perpetuating this mindset, but i cant help think such discriminatiom is a cost optimization habit. How are recruitors punished for categorically dismissing a demographic? I understand how the company is hurt, but how is the recruitor, the gatekeeper, incentivized to NOT be dismissive?
- rcarmo 8y agoI keep getting recruiter spam every week, and I've made it a point to be polite--I may take some time, but I do reply to every message that isn't an automated shotgun mail, because even though I am sometimes exceedingly annoyed at the airheadedness and calousness of some recruiters, there are often valuable insights to be had as to one's value in the marketplace, and one out of ten interchanges usually leads to meeting interesting people. Now, I'm in Europe, and around half the recruiters who figure out my age break off contact or ghost me immediately (at least until the next opportunity comes around--I had one major tech company ping me repeatedly in 2017 and break off every time...).
- w_t_payne 8y agoThere are any number of talent pools that are overlooked because of widespread discrimination. To win, you need to behave in a more rational way than the competition, which means discarding irrational biases and looking for help in places that others undervalue and disregard.
- markbnj 8y agoI kind of feel like the author is referring to Zuckerberg's famous comment about young people being smarter. I don't remember the exact quote, but it was suitably shocking and stupid so it's a candidate anyway. The thing I like about Rachel's take on this is that she gets right to the key thing: regardless of what field you're in, or how you spend your time, the vast majority of us are going to be neither horrible failures nor amazing successes. We're far more likely to just be ordinary human beings, who probably need to earn a living and have something useful to do every day. Fwiw I'm 58 and a working site reliability engineer and developer. I don't really live paycheck to paycheck, but neither can I just quit working and go instagramming about the globe. I'm fortunate to work for a very diverse company that values everyone for what they can contribute, but I am also cognizant of the people who will look at me and wonder why the greybeard never "made it." Those people probably won't "make it" either, and anyway, nobody seems to wonder why the old Italian guy in the town next to us still gets up every day and fixes shoes.
- nobleach 8y agoFrom a point of view, I might even agree with Zuck's asinine statement. When I was in my 20's, I had no idea how many things I truly did not know. So, in my limited "fresh out of college" way, I was pushing maximum intelligence. As the years have flown by, I've learned just how vast many fields are. Introspectively, I've learned that I'm not the brightest mind in any given room. As a matter of fact, I've just barely scratched the surface. Many, as they get older, realize this harsh reality. For me, I was probably very smart... and completely ignorant. In tech, this is inflated as we seem to rediscover old paradigms every few years, yet we look at those that may have lived through an earlier "discovery" as "irrelevant geezers". Many of could never dream to achieve the level of things that Alan Kay has forgotten, but we sure will treat his contemporaries as worthless. Zuck will get there some day. And I doubt history will remember his as a great visionary.
- chasing 8y agohttps://en.wikipedia.org/wiki/Dunning–Kruger_effect https://en.wikipedia.org/wiki/Dunning–Kruger_effect
- api 8y agoI would walk out at "why are you still working?" That is so many layers of ass9.
- codinger 8y agoI think this line of thinking is fallacious on the premise that the industry is growing at such a fast rate the next generation of engineers and developers is exponentially larger than the previous creating this illusion that most of the older folks must have retired by their 30s or 40s.
- geebee 8y agoGood blog post, nice write up of the conversation, but she left out the part at the end where the CEO bemoans the shortage of qualified software engineers.
- Animats 8y agoDiscrimination does pay. That's why it's so widespread.
- village-idiot 8y agoThe "Get rich and get out" expectation is in place because working at the pace that lots of SV companies demand creates an unacceptably high risk of burnout. To compensate for this risk many workers and entrepreneurs have setup a mental and social framework of "I'm only doing this until I can retire young". Of course, early retirement happens for vanishingly few workers. Some companies go Google or Uber and let the founders retire, but most do not.
- a3n 8y ago> If you want a healthy team, you're going to need a mix of people. Cutting off entire segments of the population from your company's ranks just because you don't understand their value only hurts yourself. That could be a direct quote from Peopleware.
- RickJWagner 8y agoAs a programmer in my 50s, I offer younger HN participants this idea: You will get old (if you are lucky). This will be of concern to us all at some point. I know of nobody who quit early and lived happily ever after.
- pauljurczak 8y agoI am yet another, visibly old (57), former paper (one) millionaire. I like sailing, climbing, biking, skiing, snowboarding, etc., but I have zero interest in retiring and pursuing any of these activities full time. It would become too boring. I'm self employed and work on cutting edge R&D projects I'm passionate about. I really don't care what someone's definition of success and its timetable is, neither should you.
- world32 8y agoAfter a certain amount of time (my guess is around 5 years experience) software engineers tend to experience diminishing levels of returns when it comes to productivity over years of experience. The difference between an SWE with 5 years experience and one with 1 year experience is massive, but the difference between somebody with 5 years experience and 10 years experience is much less so. I'm talking about standard software engineering roles - CRUD based applications and so on. The story is different for more specialised roles that involve expert knowledge i.e. machine learning, data science, computer graphics, info security etc. If I see the CV of somebody who has been doing the same kind of software engineering jobs for 20 years my thought is that this is somebody with no real interest in it and just does it as a 9-5 job. Now personally I don't see anything wrong with that. However, the problem is the difference between an "enthusiast" and a "9-5er" is much less apparent when they are young, their CVs will likely be very similar if they both have 3-5 years experience, however after 20 years it will become clear who is "passionate" about their craft and who just wants to go home to their family at the end of the day. Again I have nothing against people like that and I'm sorry for using the word passionate like that but I think that this is one of the root causes of this issue..