And indeed Google AI has achieved very little product wise during his time as CEO. Kind of suggests he is a big part of bureaucratic challenges they have faced
I think Jeff Dean is a great engineer, but I wouldn't hold up TensorFlow as a great example.
TensorFlow, yuck
But Ilya definitely had some big papers before and he is widely acknowledged as a top researcher in the field.
He should stay a Fellow, in a "brilliant consultant" role.
I know this is a typo, but I would love to hear about high drama involving Chef Scientists at large companies.
It would have all the nonstop action of Iron Chef, combined with the multilayered scheming of Succession... I think there's something there.
Google have oversupply of brilliant ML researchers. What they need is a engineer that sees the applications of the technology so it can be turned into a product. Someone that can bridge the gap between the R&D team and the Bureaucracy.
Want an idea for a stupid product - input - description of a girl, hobbies, some minor flaws - output - create a poem. Have been using Vicuna quite successfully for that purpose.
Can't emphasize more on how much rigorous engineering practice could accelerate research delivery. It is THE key to have a productive research oriented team.
Good research engineers are underrated, and very difficult to find.
Based on what? I've heard all the Chuck Norris type jokes, but what has Jeff Dean actually accomplished that is so legendary as a software developer (or as a leader) ?
Per his Google bio/CV his main claims to fame seem to have been work on large scale infrastructure projects such as BigTable, MapReduce, Protobuf and TensorFlow, which seem more like solid engineering accomplishments rather than the stuff of legend.
https://research.google/people/jeff/
Seems like he's perhaps being rewarded with the title of "Chief Scientist" rather than necessarily suited to it, but I guess that depends on what Sundar is expecting out of him.
When I joined Brain in 2016, I had thought the idea of training billion/trillion-parameter sparsely gated mixtures of experts was a huge waste of resources, and that the idea was incredibly naive. But it turns out he was right, and it would take ~6 more years before that was abundantly obvious to the rest of the research community.
Here's his scholar page (H index of 94) https://scholar.google.com/citations?hl=en&user=NMS69lQAAAAJ...
As a leader, he also managed the development of TensorFlow and TPU. Consider the context / time frame - the year is 2014/2015 and a lot of academics still don't believe deep learning works. Jeff pivots a >100-person org to go all-in on deep learning, invest in an upgraded version of Theano (TF) and then give it away to the community for free, and develop Google's own training chip to compete with Nvidia. These are highly non-obvious ideas that show much more spine & vision than most tech leaders. Not to mention he designed & coded large parts of TF himself!
And before that, he was doing systems engineering on non-ML stuff. It's rare to pivot as a very senior-level engineer to a completely new field and then do what he did.
Jeff certainly has made mistakes as a leader (failing to translate Google Brain's numerous fundamental breakthroughs to more ambitious AI products, and consolidating the redundant big model efforts in google research) but I would consider his high level directional bets to be incredibly prescient.
1. what was the reasoning behind thinking billion/trillion parameters would be naive and wasteful? perhaps part are right and could inform improvements today.
2. can you elaborate on the failure to translate research breakthroughs, of which there are many, into ambitious AI products? do you mean commercialize them, or pursue something like alphafold? this question is especially relevant. everyone is watching to see if recent changes can bring google to its rightful place at the forefront of applied AI.
I wonder if you know any of the history of exactly how TF's predecessor DistBelief came into being, given that this was during Andrew Ng's time at Google - who's idea was it?
The Pathways architecture is very interesting... what is the current status of this project? Is it still going to be a focus after the reorg, or too early to tell ?
DistBelief was tricky to program because it was written all in C++ and Protobufs IIRC. The development of TFv1 preceded my time at Google, so I can't comment on who contributed what.
If you initiated and successfully landed large scale engineering projects and products that has transformed the entire industry more than 10 times, that's something qualified for being a "legend".
I wrote an entire (Torch-like - pre PyTorch) C++-based NN framework myself, just as a hobbyist effort. Ran on CPU as well as GPU (CUDA). For sure it didn't compete with TensorFlow in terms of features, but was complete enough to build and train things like ResNet. A lot of work to be sure, but hardly legendary.
Google has lots of folks who had access to the similar level of resources and no one but Jeff and Sanjay made it. Large scale engineering is not just about writing some fancy infra code, but a very rigorous project to convince thousands of people to onboard which typically requires them to rewrite significant fraction of their production code, typically referred as "replacing wheels on a running train". You gotta need lots of evidence, credits and visions to make them move.
Yeah - just finished migrating a system of 100+ Linux processes all inter-communicating via CORBA to use RabbitMQ instead. Production system with 24x7 uptime and migration spread over more than a year with ongoing functional releases at the same time. I prefer to call it changing the wheels on a moving car.
No doubt it's worse at Google, but these type of infrastructure projects are going on everywhere, and nobody is getting medals.
- "I’m sure you will have lots of questions about what this new unit will look like" aka we're not going to talk about specifics in public comms
- "Jeff Dean will take on the elevated role ... reporting to me. ... Working alongside Demis, Jeff will help set the future direction of our AI research" aka Demis isn't the only Big Dog in the room anymore
I kinda liked how open chatGPT was before the heavy filtering, but I see why we need to reign in chaos overall.
https://www.deepmind.com/blog/announcing-google-deepmind
It seems that DeepMind has now gone from what had appeared to be a blue sky research org to almost a product group, with Google Research now being the primary research group.
Jeff Dean's reputation has always been as an uber-engineer, not any kind of visionary or great leader, so it's not obvious how well suited he's going to be to this somewhat odd role of Chief Scientist both to Google DeepMind and Google Research.
How things have changed since OpenAI was founded on the fear that Google was becoming an unbeatable powerhouse in AI!
Rushing it out the door in a space race model is probably not a good idea. At this point, the value proposition is moot.
As a client and even paying customer of google I don't want this AI intruded into my product experiences without a big fat OFF switch. Not because of some terminator skynet fantasy: I want an opportunity to discriminate between reality as projected from pagerank and classic NLP algorithms, from the synthetic responses from a model.
If he wanted to change things for better (in other people's eyes), he would have done a long long time ago.
My gut says that this wouldn't change things one bit. If anything, it will be worse with this giant org.
If thousands of people aren't enough, 10,000 wouldn't help much
If we wind way back to Google Docs, Gmail and Android strategy, they took market share from leaders by giving away high quality products. If I were in charge of strategy there, I would double down on the Stability / Facebook plan, and open source PaLM architecture Chinchilla-optimal foundation models stat. Then I'd build tooling to run and customize the models over GCP, so open + cloud. I'd probably start selling TPUv4 racks immediately as well. I don't believe they can win on a direct API business model this cycle. But, I think they could do a form of embrace and extend by going radically open and leveraging their research + deployment skills.