There are some... Interesting points here. I'd like to throw in an alternative point of view from someone who doesn't work as a Dev full time.

1.FOMO
"This issue is defined as a fear of regret, which may lead to a compulsive concern that one might miss an opportunity for social interaction, a novel experience, profitable investment or other satisfying event."

Missing out on a social experience? Most jobs you need to work to their schedule and socalise around that. If you are worried about missing out on something, then you would have to either catch up later, or try and swap shifts to be there.

2. Honestly I don't understand the point the author is going for here. I read a lot, doesn't mean I'll change all my code to the latest fad.

3. Because management says so.

I have been lucky, I have been able to converse with my managers a lot and been able to offer my point of view. At the same time, I have seen people lose their job for disagreeing with management. In most jobs, if you disagree, you either knuckle under or you don't get shifts.

You do what they say, how they say, without talking back. Sounds horrid, but that's how most jobs work.

4. Well... I don't argue either way on that point, it's a little too generalised.

5. Everyone is a beginner at one point. How do you pick what is best? When I'm cheffing I can't afford to perfect every type of meal- there are just too many. Instead I try and learn a little about everything, then once it's required I study more in-depth. I have done the same with coding. I
Have also done the same with working on the docks(container loading via hand, and forklift(5+10ton), also container stacking(larger forklift, plus warehouse management and the office software), Same with coding, I can write c#, vb6 and .net, frontend I can do JavaScript, php, tie into MySQL, and learn frameworks as I go.

6. I was given advice from my grandfather. If your the smartest in the room, change rooms.

While I'll be the first to say that as a saying it's a little insulting, if you take it directly, when you consider specialisations it has helped me a lot.

7. How do I approach this one.

Honestly it to non devs it comes across as rather insulting. Do I want to cook this menu over and over after I have mastered it? No.

Do I want to collate these documents again and again? No.

Do I want to write this php to store data and track the users through the site, then log it to the MySQL and ensure it reports to the manager where the user stopped on the form for follow up? No, not really.

But that's why they pay us.

Or put it another way, do I want my child to eat next week, how will i pay my rent, what will I do if my wife gets sick and can't work.

I really think it's over used, but honestly, entitled comes to mind. Most(most) people don't have the freedom to complain about a boring job. We have no choice.

I don't think what the article says is wrong per se, but it really struck me as a very (again I think it's over used) entitled way of looking at things.

Introspection isn't a bad thing, but realising you have it rather good can be a good thing too.

I hope this doesn't come across badly(also I'm using my phone so forgive any typos please haha).

Edit: fixed typos(sorry stuck using smartphone and Firefox kept crashing)