Systems | Development | Analytics | API | Testing

‍ 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.

PropTech teams sometimes plan an AI initiative by starting with the wrong question. They ask which model to use before they can answer a more basic one: is our property data ready for any of it? AI pilots may stall not because the models underperform, but because the property data feeding them is fragmented across MLS feeds, PMS records, and CRM exports, duplicated across sources, and missing the ownership, tax, and location context a model needs to reason.

For as long as there’s been a rental market, there’s been a version of this question: is the number on the listing actually the number? Ask anyone who’s built a pricing model, a forecasting tool, or a CPI estimate on top of rental data, and you’ll get the same answer — probably not, and there was never a good way to check.

As AI rapidly integrates into software development, from code generation to interface review, it promises unmatched efficiency.