Skip to main content

Waydev Adds Ability to Track How Much AI Code Winds Up in Production

Waydev today revealed it has revamped its engineering intelligence platform to provide insights into how the adoption of artificial intelligence (AI) coding tools is impacting DevOps workflows.

Company CEO Alex Circei said the overall goal is to make it easier for the leaders of software engineering teams to determine the return on investment (ROI) their AI coding tools are actually providing.

While there is little doubt that AI tools are capable of generating code faster than humans, the percentage of that code making it into production environments is often unknown. DevOps engineers need to understand where AI code is being accepted, rejected or rewritten, and whether AI-assisted pull requests pass CI at the same rate as those authored by a human.

The Waydev platform, now at every checkpoint in a DevOps workflow, captures which AI agent wrote the code across all commits, repositories, teams, and tools, along with insights into usage costs. A Waydev AI agent then provides a natural language interface to enable DevOps teams to interrogate that data. Longer term, the goal is to provide an additional speech interface to query that data, said Circei.

The goal is to create a continuous feedback loop through which the data collected can be fed back to AI coding tools to improve their output, said Circei. That’s critical because it provides a means to validate the quality of the output being generated versus relying solely on an AI agent that might only tell a developer what they want to hear, he added. Ultimately, it’s the data that will tell the actual tale, said Circei.

The Stanford AI Index estimates the median company now spends $86 per developer per month on AI coding tools, a number that is likely to climb in the months and years ahead as AI coding tools become more sophisticated. A recent Futurum Group survey found a full 60% of respondents said their organization is now actively using AI to build and deploy software, with the top areas of investment over the same period are AI Copilot/AI code tools (38%), AI agent development (37%), AI-assisted testing (37%) followed closely by DevOps (37%), automated deployment (34%), software security testing (31%). When those two statistics are correlated, it’s clear organizations are already making major investments in AI coding based as much on faith as actual tangible results.

It’s not clear to what degree the rise of AI might, as a consequence, induce more software development teams to embrace engineering intelligence platforms, but there is little doubt that managing application development and deployment is becoming more challenging as the volume of code being generated continues to exponentially increase. Regardless of approach, the one certain thing is that software development, as it was once known, will never be the same again. The challenge now is determining not so much whether or not to use AI coding tools, so much as it might be the instances where developers are generating more code than it might actually be worth creating in the first place.



from DevOps.com https://ift.tt/v472BlH
Labels:

Comments

Post a Comment

Popular posts from this blog

Claude Code’s Ultraplan Bridges the Gap Between Planning and Execution

Planning a complex code change is hard enough. Reviewing it in a terminal window shouldn’t make it harder. Anthropic is addressing that friction with a new capability called Ultraplan, currently in research preview as part of Claude Code. The feature moves the planning phase of a coding task from your local terminal to the cloud — and gives developers a richer environment to review, revise, and approve a plan before a single line of code changes. It’s a small workflow shift with real practical value, especially for teams working on large-scale migrations, service refactoring, or anything that requires careful coordination before execution begins. How it Works Ultraplan connects Claude Code’s command-line interface (CLI) to a cloud-based session running in plan mode. When a developer triggers it — either by running /ultraplan followed by a prompt, typing the word “ultraplan” anywhere in a standard prompt, or choosing to refine an existing local plan in the cloud — Claude picks u...
Post a Comment
Read more

Java 26 Arrives With AI Integration and a New Ecosystem Portfolio — What It Means for DevOps Teams

Oracle released Java 26 on March 17, 2026, and while every six-month release comes with its own set of improvements, this one carries a broader message: Java isn’t just keeping pace with the AI era — it’s actively positioning itself as the infrastructure layer where AI workloads will run. For DevOps teams managing large Java estates, that’s worth paying attention to. The Scale of What You’re Already Running Before getting into what’s new, it helps to remember what’s already in place. According to a 2025 VDC study, Java is the number one language for overall enterprise use and for cloud-native deployments. There are 73 billion active JVMs running today, with 51 billion of those in the cloud. That scale matters when you’re thinking about where AI fits in. Most of the systems where agentic AI will eventually operate — transactional platforms, backend services, data pipelines — are already running on Java. The question for DevOps teams isn’t whether to adopt Java for AI. It’s how to ...
Post a Comment
Read more

Security as Code is Becoming the New Baseline: Continuous Compliance in DevOps 

There was a time when compliance meant a quarterly ritual. Someone from security would walk over with a spreadsheet, ask a few questions, tick a few boxes and disappear until the next audit cycle. The infrastructure team would scramble to prove that yes, encryption was enabled, and no, that S3 bucket was not public anymore. Everyone felt relieved, went back to shipping features and quietly hoped nothing would drift before the next review.   That model is dead; it just hasn’t been buried yet.   The problem is not that teams lack security awareness. Most engineering organizations today understand that vulnerabilities need catching early and that production environments need hardening. The problem is that compliance has historically lived outside the delivery pipeline — treated as a checkpoint rather than a continuous practice. In a world where teams deploy dozens of...
Post a Comment
Read more