Systems | Development | Analytics | API | Testing

Every QA budget has a line item for building test coverage, but 30–50% of that automation budget ends up spent on maintenance instead of new tests. That disparity stays invisible until a release goes out, the application shifts underneath the tests, and the QA team spends the next three days rewriting broken scripts instead of finding new bugs.

Earlier this month I spent time with a group of senior executives discussing the economics of AI: what it actually costs, where the value is and is not materialising, and what the organisations that are getting returns are doing differently from the ones that are not. That conversation encapsulates why this series is called Beyond the Budget. Not because cost does not matter. It does. But because the budget is where the consequences show up.

The most useful piece of software we came across last quarter never left someone's laptop. An operations lead at one of our enterprise clients built herself an inventory reconciliation dashboard. No ticket, no sprint, no engineer involved. She described the workflow to an AI agent one evening and had something working by the next morning. A problem her team had been raising for over a year, solved by someone who has never written production code in her life.

‍ Every CFO has looked at the headcount report and asked the same question. Why does it take twelve people and four tools to do something that feels, on paper, like it should take three? The honest answer is usually not laziness or bloat. It is a coordination tax. Someone has to read an email, decide what it means, open three other systems to check context, type a response, update a tracker, and notify two other teams. None of that is hard work.

AI sovereignty has become one of those phrases that sounds precise until someone asks what it actually means. For one federal agency, sovereignty means keeping sensitive data inside accredited boundaries. For another, it means running open-weight models in a FedRAMP-authorized private cloud. In defense and intelligence settings, it may mean operating inside an air-gapped environment at IL5 or IL6.

The OctoPerf web application is a large Angular workspace: 7,786 TypeScript files, around 381,000 lines of code, 1,166 components and 2,738 test files. We have just taken it from Angular 20 to Angular 22, deleted zone.js, and replaced Karma and Jasmine with Vitest. The interesting part of this story is not the version number. It is that we got the strategy wrong first. We spent months migrating the codebase component by component, drowned in manual regression testing, and still let bugs reach production.

Unify your operational data in real time. SAP BDC Connect for BigQuery provides a zero-copy architecture to help you lower IT costs.

This is the sixth and final post in our "Features Sitting Idle" series, where we shine a light on OctoPerf features that are already in your account, ready to save you hours every week. It's a quiet but recurring friction. Teams that test regularly all end up with a preferred report layout. But in practice, that structure is often rebuilt manually after each run, or lost entirely when moving between projects.

I spent the day at NVIDIA thinking I’d be learning about all the newest models and RAM throughput achievements. Instead, a version of the future started to crystallize where AI really is good enough, pervasive and cheap(er). Let me share some of my observations and conclusions.

A practical definition of the discipline that proves a release is ready to ship, backed by evidence instead of opinion.