Earlier quoted context omitted.
i reckon we simply got offshored, since they're now building a whole new python team in munich, though i don't know whether for cost reasons or to expand the languages presence in the munich office or both.
Gateway to cheap developers in Eastern Europe, Poland, Ukraine, etc
Google lays off its Python team
351–360 of 476 posts
Re: Google lays off its Python team
#352Re: Google lays off its Python team
#353Those who are saying india are wrong, this time they are training them at munich office. Rule is simple cheap labour and more people can do better job.
Re: Google lays off its Python team
#354Re: Google lays off its Python team
#355Earlier quoted context omitted.
yes, SRE uses loads of python, despite a decade+ pseudo-mandate to encourage Go
I have heard that SRE teams can get away with this on the idea that SREs usually are not as good at software engineering as SWEs, so some bad engineering practices can fly. I never saw Python actually get used, though, in the projects I worked on.
First, there are two SRE ladders: SRE-SWE and SRE-SysEng. SRE-SWE have the same interviews and hiring bar as SWEs. SysEng have less coding interviews but I think the interview questions are more practical and less algorithm oriented.
Still, SREs are subject to the same rules and policies as SWEs when it comes to submitting code.
And in the end, I don't see why using python on some projects would be a bad engineering practice
Re: Google lays off its Python team
#356Earlier quoted context omitted.
I worked at Amazon for almost 10 years and I hate, repeat hate working with India teams. Their quality is subpar, period. No other way to put it
[flagged]
Here are some reasons why quality drops with foreign / powerless workers:
* Job is an asset. More so in poorer countries where even a low-paid US job makes a huge difference in terms of earnings in local currency. This is also, to a lesser degree what happens to visa workers. Fear to speak up. Fear to say anything that contradicts boss' plan. Losing a job like this has much more severe repercussions to the employee than if they were locals who can simply move on to another job just like the one they were fired from.
* Comprehension. No matter how good employee's English is, it's still the second language. It will make communication difficult. Beside the language, it's also often that employees who live in poorer countries have never seen either the equipment they are writing for, nor the customers who are going to use their products because simply don't exist in their countries. We rely on such shared experiences when we communicate the goals or when omitting details we even don't explicitly think about, while to the foreigners this could be completely unknown and unexpected.
* Work ethics are different between cultures. Vertical relationships in work hierarchies can be very different in different countries, which can easily prevent vital information from reaching its target. The desirable properties of employees are evaluated differently. Also, different cultures will have different ways to slack, which may not be easily recognizable to the other side.
----
In other words: it's hard to reliably transfer ideas (s.a. requirements, acceptance criteria, compensation etc.) across cultures, and this leads to failures. It's not necessary to put the blame on just one part of the team: both teams fail to communicate, and to ensure quality... but this also means that either teams' complaints are very legitimate and relate to some objective reality. Although some may start jumping to conclusions that try to explain this through racial stereotypes... actually trying to interpret the real problems through the scope of racial stereotype is what's bad about said stereotype.
Re: Google lays off its Python team
#357Google is an AI first company Google's future is strictly tied to its AI products All AI is written with Python. Google lays off all Python team. Segmentation fault
It's unfortunate that we'll likely never know what was the actual reason they decided that the old team was... overpaid? overstaffed? overly something else?
Saving money on workforce isn't the most sound business decision. After all, workforce is what generates the revenues. If you buy cheaper workforce, you should be getting ready to also lose some revenue due to quality drop... well, in large brush strokes. Maybe, in some situations the product was overpriced and making it cheaper by lowering the quality does make financial sense... Hard to tell.
Re: Google lays off its Python team
#358Re: Google lays off its Python team
#359Earlier quoted context omitted.
Why is Netflix still included? They should be kicked out, I haven’t heard anything tech about the, for years now. Then we can go with Meta Apple Google Amazon, or MAGA for short. Ok, not a good look that one.
Because they still pay $500k cash.
Re: Google lays off its Python team
#360Earlier quoted context omitted.
And how exactly do you think ads get served?
Poorly, in most cases, via various flavors of JavaScript and derived frameworks therein. Sometimes with additional overhead referred to as "targeting" which gives a worse outcome and user experience, regardless, over simpler implementations that serve to inform. Targeting forgets causality, typically. Next comes YELLING-LOUDLY-TO-COME-DOWN-TO-THE-LOCAL-CAR-DEALERSHIP-FOR-NO-MONEY-DOWN-OFFERS phase of advertisements,…
Is Google using JS for the backend ad serving / AI?