Earlier 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,…
Show HN: Hire an Oldster
131–140 of 308 posts
Re: Show HN: Hire an Oldster
#132If 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…
Re: Show HN: Hire an Oldster
#133Earlier quoted context omitted.
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,…
so you're the exception to the norm; you're one data point against... ;)
Re: Show HN: Hire an Oldster
#134Earlier 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 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. I completely agree (I'm 32), but what is worrying is the possibility of a fundamental shift that doesn't occur within individual companies but rather manifests itself as a new industry of sorts, and then a slow decline of the industry we're in right now - a paradigm shift, for…
However, the principles of engineering good computing systems will probably be pretty similar. And the higher level skills needed to be a good engineer will almost certainly be the same.
I wouldn't be so quick to dismiss soft skills as easy to pick up - well, maybe you mean soft skills like basic verbal and written communication, in which case, sure, they can be learned pretty easily. But there are a lot of very valuable "soft" skills that fall under the realm of engineering wisdom and experience.
A senior engineer can add a huge amount of value for a team - justifying a huge pay check - by having a good sense for how to design things to allow for greater productivity, when to be extra paranoid about failures, which corners can safely be cut, or how to avoid subtle but devastating pitfalls in a given domain or platform.
I think most professions are a bit pyramid shaped, with lots of people whose career trajectories don't always go up and to the right. Software development probably has a bit more of a plateau than some, but it's not the only one. Architecture, for example, is very cutthroat, with a handful of senior people who do very well, and an awful lot of disappointed later-career professionals. Even at big corporate law firms things are pretty much up or out - not everyone makes partner, and not every partner makes senior partner.
I think across all of these professions, if you want to keep moving up and/or stay highly employable (and that's a big if), then you have to always be thinking about trends in the market for your skills, and how you can stay ahead of them. It's not that different from a company thinking about how their products can continue to stay competitive in a changing market.
Re: Show HN: Hire an Oldster
#135If 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…
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…
Re: Show HN: Hire an Oldster
#136Earlier quoted context omitted.
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,…
so you're the exception to the norm; you're one data point against... ;)
Re: Show HN: Hire an Oldster
#137As an oldster - two things that I really wish my younger self would have intimately realized. 1) As a software person your are employed to Solve Business Problems - NOT to write code, NOT to write tests, NOT to hack on platforms, NOT to be Agile. Solve the problem (or add the feature) - never lose sight of this. The value you bring is directly related to this. 2) People outside software development don't give a flyin…
Re: Show HN: Hire an Oldster
#138Earlier quoted context omitted.
It is not that bad. All are in a push CMS. We have a staff for content and UX. Many sites are small. Probably total 15,000 pages for all sites. These are univeristy sites so they are not complex apps. But there is a lot of backend code and middleware for pushing files to the CDN and to an xml database.
All right. I'll be honest, I forgot what thread we were on, I was just in awe at all of the sites you run. My next thought was, "man, I wish I could use some guy like him, but he is just too expensive." One thing is for sure: there are definitely, 100%, no-questions about it, over 1 people who can be reached and who, at least for a few months, would take over 15,000 pages and 154+ sites. (An early 20s hacker). For un…
That's patently false. Undervaluing your labor because your friends work in a poorly compensated industry makes no sense. If anything the money you are earning when you are younger is more important to secure for ROI purposes.
Re: Show HN: Hire an Oldster
#139Earlier quoted context omitted.
I think it's a matter of degree. A two week crunch time every 6 months is OK, maybe even beneficial. Every month though? Not OK, and definitely detrimental.
> A two week crunch time every 6 months is OK, maybe even beneficial Being overworked nearly 10% of the time is not "OK"
Re: Show HN: Hire an Oldster
#140I would think in web development it could be as low as say, 35 but in sales, 50 may only be approaching it.