Earlier quoted context omitted.
You might think twice if you looked at the figures; the numbers in this article comparing US and UK wages are astounding: https://www.wsj.com/finance/investing/britain-white-collar-j... (and this article goes into the rationale too. Basically the idea is you're paying more than you would in a developing economy, but you can trust the team with more autonomy and fewer cultural misunderstandings, so it's an option for…
You know, it makes me wonder how hard it would be to use this divide to actually move to the EU and get residency. Then again, with so many countries having to beef up military spending and facing economic headwinds you really have to question whether all the social / quality of life programs that make europe more livable than the US would be sustainable long term either. Who knows maybe in 30 years Americans ultimat…
Google lays off its Python team
231–240 of 476 posts
Re: Google lays off its Python team
#232Outside of the ML groups, Google really doesn't like Python and there's very little of it in the codebase. This move isn't surprising in that light. Also, Google is IBM at this point, so I would expect a lot of IBM-like moves.
Re: Google lays off its Python team
#233Earlier quoted context omitted.
I'm not convinced demoralization is undesired in all cases; certainly it seems like there was a lot of frustration about workers demanding more pay, remote work, stances on various social/political issues, and so on. Making people demoralized and afraid of losing their jobs is one possible answer to that.
Theoretically you have a point. On the other hand it’s so bad for recruiting. I view companies that do large layoffs the same way I view companies that do a lot of contract hiring. You clearly don’t care about employees and their wellbeing.
Re: Google lays off its Python team
#234Earlier quoted context omitted.
I'm not convinced demoralization is undesired in all cases; certainly it seems like there was a lot of frustration about workers demanding more pay, remote work, stances on various social/political issues, and so on. Making people demoralized and afraid of losing their jobs is one possible answer to that.
t. Jerome Powell and Julie Su
Re: Google lays off its Python team
#235Earlier quoted context omitted.
Is this a genuine question? You can go for a strict, legalistic approach, like requiring cause to dismiss workers, or you can tweak incentives, like tax breaks or tax penalties encouraging desired behaviors and discouraging undesired ones. You can make arguments for why it shouldn’t be done but it is not hard to imagine things an interested government could do.
It's not that simple, long-term. Companies will just be founded elsewhere, because a hard-to-fire worker is worse than no worker. However, you could add additional layers like "if you do business in the US you must have x% of your employees here". But it's getting messy.
Either way, I think this gets away from the premise and starts getting into reasons not to do it (theoretically, you're losing some new jobs that would otherwise be created) more than reasons it's impossible
Re: Google lays off its Python team
#236Earlier quoted context omitted.
Python is mostly the Perl of the current day. And it attracts tons of beginners, that also means nearly equivalent amount of bad code(Just like in the Perl days). These days if you are doing serious work, you simply use Java. Especially if you want something running for years. Java is really the only option you have. A decade back I interviewed at a major telecommunications firm. Python was the new fashion then, they…
I guess Instagram, Threads, Reddit, Uber, and Spotify aren’t serious long term applications.
Re: Google lays off its Python team
#237Re: Google lays off its Python team
#238Earlier quoted context omitted.
then why not MAAANG?. Much better acronym, but then I just say big N.
Even better, why don’t we just get rid of the unwieldy acronyms altogether and simply refer to them as “major tech companies”? It’s clearer and avoids the constant reshuffling every time the market shifts.
Re: Google lays off its Python team
#239Earlier quoted context omitted.
in addition to contributing to upstream python, we * maintained a stable version of python within google, and made sure that everything in the monorepo worked with it. in my time on the team we moved from 2.7 to 3.6, then incrementally to 3.11, each update taking months to over a year because the rule at google is if you check any code in, you are responsible for every single breakage it causes * maintained tools to…
I was your opposite number at AWS for many years. Like you say, it was one of the best jobs I've ever had, but over there it was a career dead end. I wasn't laid off, but I had to leave it to have any hope of growing myself. I feel for ya, zem; if you ever turn up at a PyCon in person, lemme buy you a drink.
Re: Google lays off its Python team
#240i got caught up in this :( really sad about the whole thing; this was by far the best job i've had in my 20-year career (including other teams at google), and i do not know if i will ever have another one as good. we were a chronically understaffed team supporting a large part of the python ecosystem at google, and we did some amazing work over the years.
Care to weigh in about what you reckon happened? Surely the company didn't suddenly lose its need of the Python ecosystem?