I always wanted to program games. I programmed games as a hobby. When I graduated university there were no gamedev jobs in my region, so I went to work at Boring B2B java company.
After a while I moved to a bigger city and I started having friends who work in gamedev. They told me about crunch, bad salaries etc. I decided to keep doing Boring B2B stuff. But I went to a few job interviews in gamedev companies.
Every time the questions on the interviews were FUN. Like doing 3d math, some low level C, writing a collision detection function or simple pathfinding.
Just solving these problems made me giddy.
Maybe it's the nostalgia for the time I've learned these things as a teenager with no stress, or maybe it's just that it's something completely different to what I'm doing normally - but I felt great during these interviews.
But I'd have to get a huge salary cut and abandon work-life balance and I'm too old for this.
TL;DR: I think there's a lot of value actually looking at day-to-day problems you need to solve in your dream job, even if you decide it's not for you for different reasons.
Perhaps. There is also more to life than your job, family, friends, and finding love. There's things like grocery shopping, washing dishes, and going on vacation. That doesn't mean we should settle into occupations we don't like. Like it or not, your work is going to consume a lot of your time, and we should strive to do something we enjoy and find meaningful if possible. In the parent comment it sure sounds like it is possible for them to pivot, and that they might find much more happiness and meaning if they do.
I read their comment as saying that we shouldn't expect every subtask to be fun, but the overall task can still be fun. Do I want to sand wood? Not really. Do I want to grab sand paper from the drawer? No... Do I want to use a saw? A little bit. Do I want to build a chair? Yes! But if I break it down too much the overall big picture gets lost.
It's probably going to be even worse than that - HR (and everyone else) will probably then have to implement process and procedure and storage mechanisms to prove that emails have not been changed. This might mean storing emails in a document control system. Email is bad enough but now we're all going to have to keep a mirror in SharePoint or something like that.
i do this with email from my financial institutions that i care about. i login to their “secure messaging “ portal and grab pdf export of the web page.
Sometimes we find it hard to see the things that are closer to home, and presume that these phenomena are do do with other peoples and cultures.
But consider in English we currently do this blue and light blue. Where say Spanish calls them different colours - blue and celeste, and they are linguistically seen as different named colours.
Interestingly we don't do this with red, there's no red and light red, but red and pink.
Use that one. It's flour, but like for all purposes. You can make cake with it fine.