4 ms·
I think the lesson hard learned for this cohort is that some goals far in the future are now either highly likely to be unobtainable, or unwise to aim for in a
by ggm 4y ago
I think the lesson hard learned for this cohort is that some goals far in the future are now either highly likely to be unobtainable, or unwise to aim for in a world subject to AGW and future conflict (related or unrelated)
I would be amazed if there was not a similar ennui before either of the major european wars of last century.
It's not new: its the impact of seeing things your (grand-parents and) parents could achieve with "hard work" and realising you won't.
Maslow has also shifted a bit (yes, I know at some level it's been disproved or is over-stated) -"winning" at the career has ceased to be a core drive given you can be comfortable as a slacker/slow-quitter.
- herbst 4y ago> its the impact of seeing things your (grand-parents and) parents could achieve with "hard work" and realising you won't. I would argue that is not even the case. My and many grandparents have been farmers & factory workers which ment very hard and long work and your livelyhood depending heavily on external factors. Sure some would acquire wealth that is unrealistic today with 'simple work'. But my generation grew up hearing them whining about their hard lives.
- selfhoster11 4y ago> "winning" at the career has ceased to be a core drive given you can be comfortable as a slacker/slow-quitter. Slow-quitter? Do you mean, not giving out your labour for free? I don’t like that “slow quitting” has become a part of current language trends. It’s a pejorative term for what’s literally just refusing to put in more work than you’re being paid for. Nothing wrong with that.
- muthdra 4y agoYeah, but how do you draw the line? How do you figure out how to be comfortable without being a slow-quitter but also how to be friendly ambitious and creative without overstepping your boundaries at the job? I'm really bad at this. Sometimes I just regurgitate ideas I read online and I don't even realise how stupid they are until I find a counterpoint somewhere else. When I got into my current job and saw years of spaghetti PHP, all I wanted to do was change everything and even reimplement all the CodeIgniter3 stuff in Laravel so we could have a better system but my coworkers made me realise that such a change would be detrimental to the team's performance because they're comfortable with the current system. Just last week I was reading about Chesterton's fence and it definetly applies. The highest performer on my team has developed the system in PHP years ago and he's kinda the only one who really groks it. Jonathan Blow talks about highest performers as the one who know how to program better but it's actually those who know the system better and I just don't wanna step on their toes.
- Arainach 4y ago>highest performers as the one who know how to program better but it's actually those who know the system better and I just don't wanna step on their toes. It sounds like you've learned some bad habits/lessons in your career. High performers are able to learn new systems rapidly. If others are slowed by not understanding the code, that's a documentation, architecture, and occasionally tooling problem. You should absolutely be asking questions of folks with more knowledge of the system and not concerned about "stepping on toes"