Person
1 episodes · 24 quoted claims
Bill Staples says AI coding agents such as Claude Code and Codex speed up coding but create downstream bottlenecks in software delivery.
“AI and coding agents like cloud code and codex are accelerating the coding aspect of a developer's job, but it's leading to downstream bottlenecks to overall software delivery.”
GitLab calls the lack of overall innovation speed-up despite faster coding the AI paradox.
“Teams and, uh, leaders are not seeing an overall increase in innovation velocity. We call that the AI paradox.”
Bill Staples says tool fragmentation forces developers to switch contexts constantly as software moves through its lifecycle.
“And that fragmentation causes them to have to switch contexts all day long as they move the software through the lifecycle.”
Bill Staples says data residency requirements and new laws, especially outside the US, are increasing governance demands on AI use.
“there's a growing need, especially in countries outside the US, where there's, uh, heavy data residency requirements and all kinds of new laws are, you know, coming up”
Bill Staples says AI vendors often charge usage-based prices, making costs unpredictable and expanding budgets.
“often AI vendors are charging a usage-based model given the underlying cost of service, which then, uh, results in more fragmentation and expansion of budgets.”
Bill Staples says AI tools run on tokens that may not be under a common contract or cost control, risking cost explosion.
“Cause, you know, AI is powered with tokens, and, you know, they may or may not be on a common contract, um, or under cost control by the organization.”
GitLab uses the term inner loop architecture for an environment where AI agents and their data are co-located in one system.
“having an environment where both the compute or the agents, as well as the data, are co-located, we call that an inner loop architecture”
Bill Staples says actions by both agents and the humans steering them must be logged and traceable for audit purposes.
“including by the agents and the humans that were steering them, right?”
Bill Staples says GitLab has shared with customers a six-month payback period and a 483 percent ROI over three years for GitLab Ultimate.
“There's like a s six month payback period on GitLab Ultimate and 483 ROI over three years.”
GitLab calls its approach to the AI paradox intelligent orchestration and includes its Duo Agent Platform in that effort.
“We call our approach to solving this intelligent orchestration, and that's really what we're focused on now as company across the platform, including our new duo agent platform.”
Bill Staples says intelligent orchestration consists of workflows, context and guardrails.
“When we talk about intelligent orchestration, we're really talking about three things, workflows, context and guardrails.”
Bill Staples says GitLab is moving toward multi-agent swarming, in which agents work asynchronously on complex tasks.
“we're moving towards this multi-agent kind of agent swarming approach, where those agents are working asynchronously on complex tasks.”
Bill Staples says GitLab's knowledge graph indexes code semantically and links related context so it can be passed efficiently to a large language model.
“Because we index the code semantically and we stitch together all of these other pieces of context related to that code, we can hand it over to the LLM in a very efficient way.”
Bill Staples says early tests of GitLab Orbit showed agents about 40 percent more accurate and 25 percent faster.
“In some of our early testing here with GitLab orbit, we've seen, uh, agents 40 more accurate and actually 25 faster”
Bill Staples says GitLab applies the same policy gates, auditing and governance to code written by humans or by AI agents.
“whether the human wrote the code or whether the AGI agent wrote the code, the same rules apply, the same auditing, the same, you know, governance”
Bill Staples says GitLab engineers who are medium to heavy users of its platform contribute two to three times more merge requests than light or non-users.
“We see engineers who are medium to heavy users actually contributing two to three times more merge requests than those who are light or no users.”
Bill Staples says the built-in fix failed pipelines flow in GitLab Duo Agent Platform can cut pipeline failure response from hours to minutes.
“The ability to respond to a pipeline failure can go from hours to minutes.”
Bill Staples says customers who consolidated onto a single platform find AI adoption simpler because they get shared context and defined processes.
“those who have done more intentional efforts around consolidation and aligning on a platform, they simply have much simpler lives in adopting AI.”
Bill Staples predicts developers will shift from writing code to defining requirements, structure and architecture.
“I think it shifts for developers to go from writing code to really helping define the requirements for that code, how the code needs to be structured”
Bill Staples says tasks now done by senior managers and architects will become opportunities for mid-level developers.
“So things that maybe more senior managers and architects would do today become a mid-level, um, person's opportunity.”
Bill Staples says the time from creating a merge or pull request to deployment has become a new bottleneck for many teams.
“the time from a merge request or a pull request created until it's actually deployed. That ends up being a new bottleneck for a lot of teams.”
Bill Staples recommends tracking change failure rate, since more code shipped does not help if bugs increase.
“change failure rate is also a great one to think about, because, you know, it doesn't matter if you're cranking out way more code”
Bill Staples recommends tracking mean time to recovery, meaning how quickly teams restore service after production failures.
“keep an eye on mean time to recovery. When things do fail in production, how quickly are you able to get up and running again?”
Bill Staples says developer satisfaction directly correlates with software innovation and velocity.
“Because developer satisfaction directly correlates to software innovation and velocity, the time saved, uh, across the lifecycle again, end to end”