Google lays off its Python team
201–210 of 476 posts
Re: Google lays off its Python team
#202Re: Google lays off its Python team
#203Re: Google lays off its Python team
#204Re: Google lays off its Python team
#205Earlier quoted context omitted.
> very large projects with a one-file-at-a-time architecture (this was my primary job at google, ama) Is there any place where we could see such tools? A lot of the scripts that I write are contained in a single file, and I'm sure that there would be much to learn from seeing such project scripts. Thank you.
it's open source! check out https://github.com/google/pytype and https://github.com/google/pytype/blob/main/docs/developers/t... for more on the multi-file runner
Re: Google lays off its Python team
#206Earlier quoted context omitted.
Of course it does. Pretty much every FAANG, and many smaller ones, have teams for every programming language they consider important. Google has C++, Rust, Python, Java, JavaScript, and others (although I've heard that several of these teams were hard it in this round.) To take a basic example: Google has a team that works inside LLVM and Clang to improve the code it produces for Google's specific workloads. (Often t…
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 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
#207i 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.
Re: Google lays off its Python team
#208Earlier quoted context omitted.
I’m sorry to hear that. It does not make sense at all. Python cython is a complex ecosystem. It is very difficult for new engineers to pick up speed. Do you think there is some priority change? Like more focus on internal use case, instead of upstream contribution?
i doubt there is much room for a priority change. as i said elsewhere, we were a pretty understaffed team, so we were already very focused on the highest value internal use cases. we did have a couple of people who also worked on the core python interpreter, but that was only a fraction of their duties, and even our open source and upstream contributions were driven by stuff that google also needed done.
Re: Google lays off its Python team
#209This is standard recent Google. A year or so ago, they laid off GCP upper tier support to replace them with cheaper workers. PS: I won't say which MAAN_, but the recruiters are half based in India now. Coincidentally, it's a MAAN_ that laid me off previously in a relatively recent timeframe rather than attempt to find me another home internally. Brain explodes. Perhaps MAANGs need to focus more on long-term sustainab…
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.