I quit school that semester as it was clear that I would be far more effective learning on my own. What was true in my Java class turned out to be true in my Linux class, my networking class and my generals. I was WAY ahead of the curve. I now work in the industry as a full-stack Javascript developer and continue to learn each day.
Show HN: Hire an Oldster
101–110 of 308 posts
Re: Show HN: Hire an Oldster
#102Earlier quoted context omitted.
I look at the skillset between when I was 25 and now (30) and it's astounding. I can't imagine what the difference between 50 and 25 will be. If you're hiring 40-60 year olds you cannot simply hire a 25 year old and get an "acceptable tradeoff of competency" unless you didn't need anything close to that competency in the first place. Also if you're 50 and are relying on a new job's retirement program you're probably…
I'm 63 with a BS in Chemistry and MS in Environmental Systems Engineer. I was a student teacher of microbiology when I was in graduate school. I started coding fortran in HS about 1969 or 1970. > I'm pretty knowledgeable about paid search and social but I don't think my Political Science degree has anything to do with that. To imply that someone's age precludes them from understanding paid search, mobile advertising,…
Re: Show HN: Hire an Oldster
#103Earlier quoted context omitted.
> age != experience != skill Or, as a former boss of mine put it: "He has one year of experience ten times."
> "He has one year of experience ten times." Never understood this thing. One learns the most when he changes company and learnt about a new industry, with new problems, new tech, new people.
Re: Show HN: Hire an Oldster
#104Earlier quoted context omitted.
> age != experience != skill Or, as a former boss of mine put it: "He has one year of experience ten times."
> "He has one year of experience ten times." Never understood this thing. One learns the most when he changes company and learnt about a new industry, with new problems, new tech, new people.
Re: Show HN: Hire an Oldster
#105Just my 2 cents.
Best of luck.
Re: Show HN: Hire an Oldster
#106Re: Show HN: Hire an Oldster
#107If you take a survey of hiring managers they will point to three primary reasons that candidates 40 - 60 have a harder time finding jobs: 1) They are typically more expensive than "market" for the same role a younger person can fulfill at acceptable tradeoff of competency - higher salaries, higher related costs like healthcare for a family, expectations around retirement programs, etc. 2) They are less flexible - the…
> unwilling to run the same 60 hour gauntlet that a 25 year old _can_ etc. Older people _can_ run 60 hour gauntlets. We're just wise enough to know that it leads to no good outcome.
Hence, you won't get hired.
Re: Show HN: Hire an Oldster
#108Earlier quoted context omitted.
It's a weird experience if you're a clever youngster. I liken it to speed vs torque. I have to rely on being fast and being able to scan a problem as fast as I can to understand it. But an older engineer will just know the lay of the land. I had this happen a lot with an older electrical engineer. He seemed slow and I looked to run circles around everyone, but he could point to things as a root cause before I even un…
This is fundamentally true and basically is a great anecdotal argument for why we have the concept of a PE. Edit: Context is America and also obviously this isn't a thing in software but is very much the normal way of doing business in classical engineering.
Re: Show HN: Hire an Oldster
#109You are only as old as you believe you are. I'm 42 and won't trade spot with any 20-something for a job. The knowledge and experience I have today, most 20-something would love to have but.. they have to live some 20 years to now gain. WTG putting this message together, good luck!
Well, I'm 42 and I believe I'm 20... until I spend any time hanging around 20 year olds.
Re: Show HN: Hire an Oldster
#110I was recently working with an older developer. I don't know, maybe of 65 or 70 years. He was working on aerospace network intrusion detection systems, and I was helping him set up a simulation system. He was slinging around low-level computer architecture terminology, while I was quickly trying to access what I remembered from a college class 15 years prior, just to keep up with the conversation. Older programmers a…