Good morning. Time and again, we are told that AI requires us to move faster. Most of us already feel like we are moving quickly, thank you very much. Speeding up is easier said than done. I asked Google’s Ryan Salva, who leads product teams responsible for developer tools and services, for insight into how that can actually work.
He joined Google last year after leading developer tooling at Microsoft and Github, which it owns. He's been responsible for Google's products including Gemini CLI, an open source AI agent for developers, and Gemini Code Assist. Here are some edited highlights of our conversation at Google offices in New York.
WSJ Leadership Institute: Some people say AI is going to kill software. What do you think about that prediction?
Salva: It’s overblown.
It's still software we're shipping. We are into a higher level of abstraction though, much in the same way that no one writes ones and zeros anymore. Even those folks who are still writing code are writing with an intermediate language like Java or C# or Rust, right? The large language model is allowing us to operate at another layer of abstraction where we are able to express through natural language and intent. But the engineering part of it, the architecture part of it, that is still very, very much at the core of what every engineer needs to do.
The product that they're shipping isn't code, the product they're shipping is software .. an application that does the thing that fulfills a business need.
WSJLI: As AI allows engineers to move faster, how do organizations adjust?
Salva: This new velocity is fundamentally reshaping engineering teams. Whereas previously, you might have a director with 30 or 50 engineers who were assigned an area, and they might perform a major release once a month.
Now what I see happening is that you've got teams of maybe three to six engineers, but there's many of them working in parallel. You're able to work through more of your backlog. You are often able, then, to ship more frequently, which means that your customers are getting more value, more quickly.
And as the engineering teams can move faster, it allows other parts of the business to both iterate and kind of move faster as well. I do think that it causes some challenges.
WSJLI: How so, and what do you do about that?
Salva: I was meeting with our go-to market team and our revenue team the other day, and one of their complaints to me was that we were shipping too often, that we were literally outpacing their ability to keep up. I realize that sounds like a humble brag. It's actually not intended to be. It's actually a real business challenge. As your engineering teams move faster, it means that all of the human aspects of it need to find a way of coming in lockstep with each other. And that may mean that your engineering teams need to adjust in order to meet the more human process-oriented pieces of the business.
I actually see that we end up with a lot more embedded engineering teams directly into the organizations.
If I were to maybe counsel or coach my peers and my colleagues in these roles, I would advise them to reserve learning time and to create regular connection points with their engineering teams. Those engineering teams want to ship software that is responsive to the needs of the go-to-market team, the customer support team, the finance team.
And the more that we create, the proverbial silo between our teams, the less effective, the organization at large is.
WSJLI: And how do engineering teams adjust?
Salva: If it used to take a month to deliver a major release you had to be precious, really, about that code.
It was both emotionally difficult sometimes to throw it away, but also just expensive. As we are moving more and more towards using AI, it means that we can build that software much faster. Our ability to try a thing and throw it away is much more accessible, and we're much more willing to take a little bit of a risk here and there.
How is your company getting engineers and business teams to work together? Use the links at the end of this email and let us know.
|