This seems like a promotional post where DeepMind is advocating a product by Cue. It looks cool, and I'll be very interested in general, but maybe when Google offers the same, I'm not super interested in having another company's agent on my computer.
I'm willing to bet that many start off without any notion of workflows thinking they're not going to need that or not thinking at all, and then add complexity step by step until it's an unimaginable tangled mess.
In addition, Alphabet has reached an agreement to sell $10 billion of stock to Berkshire Hathaway Inc. in a private placement, comprised of $5 billion in Class A Common Stock at a price of $351.81 per share and $5 billion in Class C Capital Stock at a price of $348.20 per share.
This investment by Berkshire Hathaway adds to the position it has built since Q3 2025.
Pretty much anything for which you'd need intelligence of any kind. Questions such as: Do these two paragraphs have the same semantic meaning? Do they have the same sentiment? Do these two methods have the same contract? etc.
Not all documents our code and even with code deterministic tools gets you only so far.
I built a more naive version for our team using Copilot and GitHub actions and it works quite well (wish I had metrics too). The team loves it.
The ROI here is so high that I don't mind using the strongest model available for the actual code review. I don't trust Sonnet and such. Just let Opus or GPT 5.5 do the whole thing and pay a bit more for less complexity.
For simple use cases, sure. But when you start to have to build artifacts with different dependency versions, JDK versions, architectures, etc., then this complexity has to be somewhere, and Gradle can do that for you if you know how to wield it.
We are a large enterprise shop with many projects being built on different machines, architectures, technologies, etc. We took the time to become decent in Gradle, and it works great for us.
Gradle is really powerful if you know what you're doing and you take the time and effort to keep your build optimized, sane, and working.
I recently built a Gradle plug-in that allows us to build native components on a remote system (z/OS) and integrate these tasks and artifacts with the native Gradle model so that Gradle takes care of caching and parallel task execution. I'm sure this is possible with other build tools as well, though, but the Gradle model fit our use case nicely.
I think any complicated build system will eventually devolve regardless of the build tool if it's not properly maintained; the variability of the required tasks is just too high.
Gradle does seem to be moving fast with regards to Java support in general changes and improvements in the build tool. It takes effort to keep up, but it's worthwhile.