5 ms·
I think this is a huge part of it, folks who stop "keeping up" with the technology eventually find there is a huge amount of catching up to do. When that happen
by ChuckMcM 13y ago
I think this is a huge part of it, folks who stop "keeping up" with the technology eventually find there is a huge amount of catching up to do. When that happens, especially if there isn't a lot of runway, it can be difficult.
I remark to folks all the time that you can take someone right out of high school, and have them spend about 2000 hrs learning about "computers" and now they are 'hot shot programmers' that are in demand. 2000 hours is a bit more than a year at 5 hours a day factor in that the math, and intro classes aren't necessary for someone who has both done the degree before and spent some years working in the field, and I suspect that any engineer taking a 6 month sabbatical could be right back to current. And completely current with the wisdom of organizational dynamics, work habits honed by years of what worked and what didn't, that person should be like gold.
The place where I feel sad is when someone says "I've been unemployed and spent the last 6 months sending out resumes and no one will call me because I'm old." Had they instead spent that six months re-tuning old talents, sending out the occasional resume, and building stuff, that seems to get people hired regardless of age.
- tsotha 13y ago>Had they instead spent that six months re-tuning old talents, sending out the occasional resume, and building stuff, that seems to get people hired regardless of age. There are two problems with that logic. The first is if you have only six months of experience doing something your pay is likely to reflect that. Second, look at it from an employer's perspective. You can hire a twenty year old or a fifty year old. They have the same experience with whatever the latest thing is. The twenty year old has the energy of youth. No wife or children. He may come in hungover occasionally but with enough Red Bull he'll bounce back by noon. The fifty year old is slowing down. He takes drugs for his blood pressure that make him tired. He has ailing parents and teenagers at home. Who do you think is going to be more productive? Who's going to put in 16 hour days at crunch time? You can't play to a young man's strengths if you want to compete with young men when you're over forty. IMO you'd be better off as the last guy who knows COBOL than just like every other mobile programmer with six months of experience except older and slower.
- ChuckMcM 13y agoI'm not sure I see this: > The first is if you have only six months of experience doing something your pay is likely to reflect that. My experience is building things has very little to do with the current frameworks and languages. Building a payroll system with a NoSQL back end and an AWS front end is "different" than building the same with an Xwindows client and an Oracle back end, but the things that may a payroll system "good" or "bad" often have nothing to do with the bricks and mortar and more to do with the kinds of things that typically go wrong or requirements that are left unstated. Someone with 20 years of experience writing programs will often know that part much better than someone who has yet to experience them. > You can hire a twenty year old or a fifty year old. They have the same experience with whatever the latest thing is. The twenty year old has the energy of youth. No wife or children. He may come in hungover occasionally but with enough Red Bull he'll bounce back by noon. That however is what sounds like actual age discrimination, that might be like not hiring a woman because "Darn it she decides to have a kid and then what? Force me to pay maternity leave? No thank you!" or "Hire that blind guy? Really like we all we need around here is someone whose computer keyboard costs more than a Retina Macbook, No thank you!" or any number of people "not like you." > Who do you think is going to be more productive? Who's going to put in 16 hour days at crunch time? That is a good question, but one where the answer might surprise you. One of them might not have to put in 16 hours a day a crunch time, and one of them might be more productive in 6 hours than the other is in 12. But if you assume work performance based on age, gender, race, religion, or sexual orientation, you will always be doing it wrong.
- codygman 13y agoHonestly I've found for the most part that those who work 6-9 hours get more done than those who work 10+. Usually those spending 10+ are playing catchup or learning a new technology at the same time.
- pmiller2 13y agoI recently had an interesting experience interviewing with a startup (which shall remain nameless). During the interview process, we had a nice discussion about sustainable development practices, and I talked about my willingness to put in the occasional long day as needed. When we got to the point where they expected me to work 60+ hours a week for the next year, they cut me loose. I could have probably done it, but really only 6-9 hours a day, like you say, would have been actually working on what they were paying me to work on. I'm still not sure how a schedule like that could ever have been considered sustainable for anyone who wants to have any of: a social life, family, or professional development time (going to meetups and such).