Its really not that easy to build teams in dramatically different geographic locations. Ignoring all the legal waters you have to navigate you typically slow down output while your management complexity explodes. Not saying it can't be done. Just that in my experience it typically doesn't have the effect people initially think it will.
Tell HN: Don't root for WFH, it might destroy well-paying jobs
91–100 of 165 posts
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#92Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#93Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#94So its not nice working amongst people who can be even more talented and picked from a wider pool of people?
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#95Hot take: if you're a mediocre dev, maybe be worried; if you're in a niche and have deep expertise you'll be fine.
This has a flywheel effect where once you start gathering critical mass in a place, the original experts lose their edge eventually. See what happened to manufacturing, where China is leaps and bounds ahead of Western nations.
Wait, no they aren't. They do a lot of labor-intensive, non-specialized manufacturing but other countries are still way ahead where it matters.
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#96Your arguments really need a jump in logic to be accepted. They also completely fall apart when you realize two things: Offshoring has been happening for decades. H1B abuse has been happening for decades. Yet salaries rose.
Summary: outsourcing was never really going to work due to collaboration hurdles. Current model is to replace one US-worker at a time with a non-US-worker from the same timezone. Much more effective and much more lethal to US workers.
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#97What percentage of a pay decrease would you accept to work from home? If your job said come into the office, or take a 30% cut and work from home, would you do it?
My company is already on 4 and may soon move to 5. Is that a future you want? You may take a 15-20% paycut and enjoy your suburban luxury lifestyle for a few years. Beyond that, as the WFH from foreign countries kicks in, you will see that there won't be many job openings at a high salary for your role.
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#98I'm in SV. What a horrible take. Globalization of tech jobs is net positive for the whole world including the US. We're all gonna have more thing made cheaper and faster, isn't that great? I can see how you can argue it's not the case with some industries, e.g steel and coal (see poverty in Appalachia), because it's hurting those communities. But this is tech, we already have it way too easy. I say let's double down…
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#99I've been sounding this alarm for years, on def ears. Nobody wants to hear it but the truth has never been more clear. There is a HUGE pool of talented, hungry developers around the world who want YOUR job for 1/4th of your pay. The second US companies open their doors to those engineers, we will see dramatic decline in SW salaries. What has held this at bay so far as definitely been the companies that don't allow re…
Re: Tell HN: Don't root for WFH, it might destroy well-paying jobs
#100Earlier quoted context omitted.
If this problem was only narrowly applicable to SV, then yes, you might have a point. I am talking about a majority of new hires being in other countries. At that point, to spite SV rich techies, you are rooting for destruction of a good pool of middle class jobs for the entire US. Is that really what you want?
> I am talking about a majority of new hires being in other countries. That would be no different from the mid-2000s outsourcing trend, which never really worked out either. There were just lots and lots of horror stories where quality and productivity would take a nosedive whenever those outsourced teams were involved.
I have seen both, 2000's outsourcing and what is happening now. It is a very different game now and far more dangerous to US techies.