AI-assisted coding is accelerating software development so quickly that enterprises are struggling to keep pace with validating the code they produce, according to an analysis published this week by InformationWeek. Two companies addressing this problem raised a combined $595 million in funding this week: AI code review company CodeRabbit reached a $1.5 billion valuation after its latest funding round, while software testing platform Blacksmith raised $45 million at a valuation approaching $550 million. The simultaneous emergence of these companies points to the same shift — AI is helping organizations produce code faster than many can confidently evaluate it.
The change reverses a familiar constraint in software development. For years, engineering organizations focused on making developers more productive and reducing the time required to write and ship code. Now, the limiting factor is increasingly what happens after the code is produced. One consequence is that engineers don't have the same context for AI-generated code that they would have for code they wrote themselves — the reasoning behind implementation decisions is missing, even when the resulting code appears sound. That makes validation more complex than simply checking whether the code passes a conventional suite of tests, since reviewers also need to establish why the code was written as it was and whether it behaves correctly in situations the AI may not have anticipated.
"AI has done two things: It's increased the rate of code generation, but it's also exposed the bottleneck of checking, validating and sanitizing that code," said Richard Simon, CTO at T-Systems International. "We're moving away from developers being the bottleneck to the testers being the bottleneck." Tommy Tran, a software engineer at Meta specializing in AI and machine learning infrastructure, argues that enterprises should anchor tests to requirements and system contracts rather than to the implementation produced by an AI system — otherwise, organizations risk creating a closed feedback loop in which AI-generated code is being evaluated against AI-generated assumptions. Balaji Srinivasan, senior director of engineering at LinkedIn, said conventional coverage metrics can obscure whether tests are actually validating meaningful behavior, adding that "useful coverage of code becomes a more important metric than the traditional coverage numbers that we see."
The shift is forcing enterprises to reconsider when validation happens in the development process. In a conventional development process, testing can happen after developers have completed their work, but AI can generate code in parallel and iterate on it rapidly. If testing is treated as a discrete stage at the end of development, several code changes may have accumulated before the organization has established whether those changes work. Simon points to AI model provenance, automated review, dependency checking, security scanning, and test adequacy as controls that can and should be incorporated into the development process, with human approval reserved for changes where the potential consequences warrant it. The result would be a development lifecycle in which validation happens continuously, rather than acting as a gate at the end.
Whether enterprises can make that shift at scale depends partly on the maturity of their existing testing infrastructure. Organizations with strong automated testing can increase code volume without requiring a proportional increase in manual review, while those without may struggle. Srinivasan noted that if test coverage is poor and an organization is dependent on manual testing to uncover bugs and qualify builds, then it can't realize the full benefits of AI-assisted coding since a human is required to validate the code. There's also an economic case for buying rather than building those capabilities — Tran said internal validation systems require ongoing work as AI models, security risks, and development environments change, while specialized vendors can spread that investment across customers. But enterprises that purchase these types of products aren't handing responsibility for software quality to those vendors — the tools can review code, run tests, and identify potential problems, but organizations still determine their requirements, risk tolerance, and whether a change is ready to ship. For enterprise IT leaders, the value of faster code generation increasingly depends on whether the systems around it can validate that code just as quickly. The pressure to industrialize testing infrastructure may ultimately separate organizations that can scale AI-assisted development from those that can't, particularly as the gap between code production and validation widens.