I work at SAP. I'd say we're
pretty neutral on age - I work with people 20 years younger to 2 years older than me.
I think I've put in maybe two 40+ hour weeks in the past 5 years. I manage several devs and I hate dashing the younger (or ambitious) ones' dreams of resume driven development. My team handles a legacy system that neither crashes frequently nor needs extensive refactoring. "Sorry, cutting up and containerizing the system and using Kubernetes to deploy isn't worth the headache."
I know I'll keep getting promoted (and so will my reports) if I make sure my manager doesn't get calls from his manager asking why there are service outages.
Things move very slowly on purpose. It's better to miss delivery dates than to get bad press or run afoul of laws (which begets bad press).
What do you recommend to the younger or ambitious devs who want to grow in their career -- do you send them to training or let them have a side project of some kind so that they still have a somewhat valuable resume, or is it more a question of trying not to get junior devs (who need the resume building badly) in the first place?
I'm curious because I work at a big company but not in a maintenance or operational role so I'm not sure what an "ideal" resume or career track looks like for such people.
I think I've put in maybe two 40+ hour weeks in the past 5 years. I manage several devs and I hate dashing the younger (or ambitious) ones' dreams of resume driven development. My team handles a legacy system that neither crashes frequently nor needs extensive refactoring. "Sorry, cutting up and containerizing the system and using Kubernetes to deploy isn't worth the headache."
I know I'll keep getting promoted (and so will my reports) if I make sure my manager doesn't get calls from his manager asking why there are service outages.
Things move very slowly on purpose. It's better to miss delivery dates than to get bad press or run afoul of laws (which begets bad press).