Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

Does the UK really need Gigawatt data centres? | Civo Navigate London 2026

Everyone's racing to build gigawatt AI factories by 2035. What if the faster route is already plugged in? Swarms of agents need far more compute than a chat prompt ever did, and the scaling laws say demand isn't slowing. But in the UK, anything over 15MW can mean waiting until 2032 or later for a grid connection. So the panel makes a different case: smaller sites on existing power and fibre, linked into one national campus, live in less time than a single mega-build.

Before you build your own internal platform, run these numbers

"We'll just build it ourselves" is usually said with confidence and a rough headcount estimate. Six months later, the team that was supposed to spend two sprints on it is still maintaining it a year in, and the platform that was meant to save engineering time has become one of the things engineering time goes to. Build isn't automatically the wrong call. Sometimes it's the right one.

AI Can Write Infinite Code. But Can We Ship It Safely?

AI is making code generation faster than ever. But writing code is only half the battle. Neil Watkins from Burns & McDonnell explains why the next big challenge in AI-driven software development isn't generating more code. It's making sure that code can be tested, secured, and deployed safely. As AI accelerates development, businesses need to rethink how they manage risk and ship software with confidence.

Git worktrees: How to work on multiple branches at once

Git worktrees let you check out multiple branches of the same repository in separate directories. Each worktree has its own files and staging area, but they all share the same Git history. You can work on several branches without repeatedly switching between them, stashing changes, or cloning the repository again. Worktrees are especially useful when working with coding agents. Tools like Claude Code, Codex, and Cursor can use them to handle multiple tasks in parallel without editing the same files.

Shipped: Slice AI spend eight ways in AI Explorer

You can already break down cloud spend by team, product, or customer in Explorer. But AI spend has been harder to decompose. Which models is each team running? What activity is driving the cost growth you saw this month? Before AI Explorer, answering those questions meant exporting raw event data and building your own breakdowns, or waiting days for reconciled billing to land in Explorer.

Adding friction to your AI spend isn't saving money. It's costing you growth.

Enterprises are putting hard ceilings on AI spend. Accenture now centrally funds $29 a month per person for Claude and charges anything above that to a project budget code. Uber used up its 2026 AI budget in four months and restricted access. A cap stops waste and useful work at the same rate. The alternative is seeing AI cost by team, by project and by outcome, then funding what returns. Companies spent the past year telling employees to use more AI. Now a lot of them are putting a lid on it.