4 ms·
No connection to Google, but I'd be cautious about ageism in this type of thinking. Been at places before where young guys mostly burn themselves into the grou
by gedy 4y ago
No connection to Google, but I'd be cautious about ageism in this type of thinking. Been at places before where young guys mostly burn themselves into the ground "working hard" coding all sorts of stuff that really didn't matter, or sacrificing their personal time and life for code. The older guys were considered "unmotivated" because they didn't overwork when they knew it wouldn't matter.
- omeze 4y agoYes, didnt mean to be ageist. Its a mindset thing- 22 y/os would go to Oracle knowing they could clock in 25 hours a week. I’ve worked with 40+ y/o engineers who still show up fresh everyday and work a standard 40 hours, but were efficient, great teammates and leaders.
- _nalply 4y agoPlaying the devil's advocate: How would the older guys know that their work didn't matter? My personal experience: 2001 I got assigned to an internal project to keep me busy. When planning and getting feedback from the internal stakeholders I realized that they weren't interested in the project. I slacked off, because there was nothing else to do. I got laid off six months later.
- gedy 4y agoI guess I was referring to more optional type work like inventing their own frameworks and abstractions, refactors for code style, major rework of some in-house blob of code that could easily be done with an off the shelf library, etc.