> 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.
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"
> 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.
That wisdom makes you of negative business value to your manager, since he still believes 60-hour gauntlets are an intrinsic part of being on time and under budget. Hence, you won't get hired.
I'd be happy not to be hired by such a manager. Crunch time happens sometimes, and you gotta do what you gotta do. But 60 hour weeks as a matter of course are a dealbreaker for me.
As 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…
I agree with both of these and would only add a #3.
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.
What is a PE?
Professional Engineer. It's an anointed position from an association of engineers, like an old-time guild. There's a duty to mentor youngsters, and a requirement for youngsters to spend time being mentored before getting PE status themselves.
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.
What is a PE?
I hope he clarifies, but I think it stands for Principal Engineer.
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,…
If 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.
Older people are more likely to have stable homes, relationships, expenses and goals. This can also translate into a "comfortable groove" of 60+ hour weeks that goes on indefinitely, simply because it's not a grueling ordeal.