Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Generate a Puppet Module Using GitHub Copilot and VS Code
This tutorial shows how to use GitHub Copilot with the Puppet Model Context Protocol (MCP) server to generate, validate, and refine a Puppet module—even if you’re new to Puppet development.
7 reasons Civo's UK sovereign cloud secures regulated workloads
Sovereignty is one of those words that gets stretched until it means almost nothing. Vendors apply it to any infrastructure with a UK data center, regardless of who owns the parent company or which jurisdiction's courts govern the contract. For a developer running a personal project, that ambiguity is probably fine. For a fintech under FCA oversight, an NHS trust processing patient data, or a legal firm handling privileged communications, it isn't.
How to Catch AI Code Mistakes Before They Reach Production
AI can write code fast, but it makes mistakes humans often don't. In this session from Ole Lensmar, CTO of Testkube, breaks down the real quality risks of AI-generated code and how engineering teams can build guardrails before those bugs hit production. What you'll learn: Common mistakes LLMs make (and which ones are unique to AI) Whether you're a developer leaning on AI to ship faster or a QA lead trying to keep up with the pace of AI-generated code, this talk gives you a practical framework for staying ahead of quality issues.
Kosli and Adaptavist Partner to Automate Governance for AI driven Software Delivery
Today, Kosli and Adaptavist announce a strategic partnership to help regulated enterprises automate governance for AI driven software delivery - making it automated, continuous, and evidence-driven rather than a manual checkpoint that sits apart from DevOps and CI/CD. Adaptavist brings deep enterprise DevOps transformation expertise: assessment and strategy, DevSecOps integration, developer experience, and implementation across Atlassian, GitLab, and AWS.
Software development standards and best practices
Every engineering team wants to ship high-quality, reliable software quickly. Historically, engineers used a few guiding principles to help them consistently write clean code: keep code DRY, shift security left, write solid test cases, own your services, document your runbooks, and more.
Phil Christianson on Balancing Innovation and Reliability in Modern Product Teams | Harness Blog
At SREday NYC 2026, the ShipTalk podcast spoke with Phil Christianson, Chief Product Officer at Xurrent, for a leadership perspective on the intersection of product strategy, engineering investment, and platform reliability. While many of the conversations at the conference focused on tools, automation, and incident response, Phil offered a view from the C-suite level, where decisions about engineering priorities and R&D investment ultimately shape how reliability practices evolve.
Deterministic by Design: How Harness Grounds AI Agents in Structured Data | Harness Blog
When AI agents operate across a multi-module platform like Harness (from CI/CD to DevSecOps to FinOps), the number one goal is to give you answers that are correct, consistent, and grounded in real data. Getting there requires a deliberate architectural choice: when a question can be answered from structured platform data, the agent should use a schema-driven Knowledge Graph rather than raw API calls via MCP. The principle is simple: if the data is modeled, retrieval should be deterministic.
Using Open Policy Agent (OPA) with Terraform: Tutorial and Examples [2026]
Infrastructure as Code (IaC) solves the provisioning problem. It doesn't solve the governance problem. You can version your Terraform configuration, run it in a pipeline, review every pull request — and still deploy an S3 bucket with public access, a VM with no encryption, or a resource that exceeds your cost budget. Nothing in the standard IaC workflow checks for those things. The reviewer has to know what to look for. And they won't catch it every time. Policy as Code changes that.
How instant environment cloning reduces the "Triage Tax"
The most expensive hour in software engineering is the hour spent trying to figure out why a bug exists in production that doesn’t exist anywhere else. For many teams, the first 70% of a debugging cycle isn't spent fixing code; it is spent on "plumbing." This is the time lost to reproducing the issue, wrestling with environment drift, and sanitizing datasets just to get to a starting line.