mihai_maruseac's comments

mihai_maruseac | 1 year ago | on: Google lays off its Python team

The issue is that now they're hiding. Those who do the decision no longer send emails, no longer show up in townhalls (if they organized).

There was a townhall for the past wave of layoffs where the exec in charge preferred to take the meeting via video call from a huddle in the same building as the auditorium where the townhall was taking place. Just to not be seen with the employees.

mihai_maruseac | 1 year ago | on: Google lays off its Python team

Yes, production code is C++, but the way the models are built is Python code, colab, save via Orbax/TF SavedModel, etc and then serve in C++. All (most, to hedge it) development is done via Python.

I don't directly develop the models, I played with some for fuzzing [1] and I'm working on security for them [2]. And, before joining GOSST, I was leading the OSS DevInfra team in TF. I still have the most number of commits made by a human [3] even after 2 days of leaving the team, though I see the next person only needs 4 more :)

[1]: https://security.googleblog.com/2023/08/ai-powered-fuzzing-b... [2]: https://security.googleblog.com/2023/10/increasing-transpare... [3]: https://github.com/tensorflow/tensorflow/graphs/contributors

mihai_maruseac | 1 year ago | on: Google lays off its Python team

Google 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

mihai_maruseac | 1 year ago | on: Google lays off its Python team

Based on the contents of the blog (as that's the only think I can talk about -- I was in the team pre 2022), it's mostly dead.

JAX (and Keras) is where the push is now. And, grudgingly, PyTorch

page 1