Earlier quoted context omitted.
[flagged]
I'm a bit surprised anybody with DevOps in their name would be unclear about the benefits of having specific roles devoted to what might seem to the uninitiated like just some tiny corner of the development process. Past a certain scale, things can't be covered by just having anybody pitch in as required and everybody collectively muddling through.
Google lays off its Python team
121–130 of 476 posts
Re: Google lays off its Python team
#122Earlier 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…
Re: Google lays off its Python team
#123Earlier 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…
> 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.
Re: Google lays off its Python team
#124Earlier quoted context omitted.
they are building a new python team from scratch in munich, for whatever reason. yeah, it doesn't make sense to me either.
Salary, right? I have to imagine at one point the gap between US devs and European devs is starting to be felt
Re: Google lays off its Python team
#125This 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…
Re: Google lays off its Python team
#126Meta is clearly driving most of CPython efficiencies. The projects listed are mostly stable so it's smart of Google to let the community drive it forward and they just use it ("we had managers that were extremely good about work life balance" and "marathon not sprint" should tell you all you need to know.) Python inside Google, for non-AI stuff at least, feels quite a bit different than with different defaults than t…
If you prioritize busyness you will get busyness but not necessarily productivity.
Re: Google lays off its Python team
#127Earlier quoted context omitted.
What people / HN don't understand is does the work they do really a 10 person $5Million per year value to Google or can it be done by Two really smart Python Experts. The problem with Tech layoffs is not that they weren't doing important work, it is that there were large teams to do what essentially can be done by two-person teams.
That really doesn't jive with this description of how much they were doing. Let me guess, this mythical two person team could also build Twitter and Uber over a weekend? https://news.ycombinator.com/item?id=40176338
Re: Google lays off its Python team
#128Earlier quoted context omitted.
There’s a ton of python all over the place. You don’t know what you’re talking about.
maybe they plan to adopt mojo
Re: Google lays off its Python team
#129The post suggests their jobs were offshored. Is this a common practice versus just closing the roles? I feel like US legislators should do more to protect domestic jobs from domestic companies, or else they’ll face the same eventual collapse as in manufacturing.
This might be my prejudice but when someone talks about offshoring a role, moving it to Munich isn't the first thing that comes to mind. It may be slightly cheaper than California but not by so much that if expect it to be the main reason for doing so.
(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 offshoring higher-value work)
Re: Google lays off its Python team
#130The post suggests their jobs were offshored. Is this a common practice versus just closing the roles? I feel like US legislators should do more to protect domestic jobs from domestic companies, or else they’ll face the same eventual collapse as in manufacturing.
How do you "protect" a job?