It’s just good planning to have multiple potential forms of income. Programming might be the thing I do that can pay the highest, but I have plan B, plan C, and plan D ready to be put into action if I suddenly don’t have a career in software engineering, or I don’t want a career in software engineering.
Interestingly enough, having options also puts you in a stronger position when discussing salaries and benefits with your employer or perspective employer.
I would like to read more about that if you would care to share more details. I cannot imagine a career in anything but software, but this year has me very low on contract work and some backup plans are something I am trying to devise.
DevOps reports research seems to bear this out, but you never know if management will figure that out before they make the decision.
* remote work widens the competitive playing field. Boo hoo. If you think non-remote work is somehow immune to offshoring, take a look at the last three decades for counterexamples.
* remote work enables you to be forgotten: sure, if your managers suck. Again, see gestures at the entire industry for examples of people getting "forgotten" at in-person offices.
* remote work breaks large companies: better phrasing - "remote work makes it plainly obvious that large companies are broken"
* remote work can stifle your career growth: again, sure - if your managers suck. They likely suck in person too, in that case.
* Conclusion: "what if instead of remote work companies just stopped acting like companies act"
As a content marketer, Sean is doing a great job of supporting a target customer persona: sucky bosses who are desperate to find a way to get back to an arrangement that makes it harder to spot how much they suck. I'm sure he'll get a lot of clicks.