Skip to main content

Posts

Why the Software Development Tools you Choose Directly Affect Your CI/CD Reliability 

Most conversations about CI/CD reliability start in the wrong place. Teams debug flaky pipelines, investigate intermittent failures, tune alerting thresholds and optimize build times. All of that work is legitimate. However, the decisions that most directly determine whether a CI/CD pipeline is reliable or not were made months or years earlier, during tool selection. By the time teams are debugging pipeline reliability, they are usually dealing with the downstream consequences of upstream decisions that seemed reasonable at the time.   The software development tools a team chooses shape their CI/CD pipeline in ways that are not always visible during evaluation. Understanding those connections is the most practical starting point for teams that want reliable pipelines rather than better pipeline firefighting.   The Integration Surface Problem   Every tool in a software development stack creates an integration surface. Integration surface is the set of connections a tool has with oth...
Post a Comment
Read more
Recent posts

The Death of the Four Golden Signals: Designing Telemetry for Non-Deterministic Infrastructure 

In complex software systems, our traditional definition of operational health has always been comfortably binary. For over a decade, site reliability engineering (SRE) teams have relied on the industry-standard ‘Four Golden Signals’ — latency, traffic, errors and saturation — as the ultimate truth of platform stability. If our API-response times are hovering at sub-100 ms, network throughput is steady, CPU cores aren’t pegged and the HTTP 500 error rate is flatlined at zero, we sleep soundly. We check our Grafana dashboards, see an entirely green pasture and assume that our platform is delivering flawless value to the business.   Then came production AI.   With organizations rapidly transitioning from deterministic, code-driven microservices to   non-deterministic, LLM-powered applications, this foundational telemetry framework is facing a quiet crisis. In an AI-driven ecosystem, a system can be structurally flawless while failing functionally. An API gateway can return a crisp ...
Post a Comment
Read more

Harness Acquires Codecov to Identify Untested Code

Harness this week acquired Codecov , a provider of a platform that analyzes the percentage of a codebase that has been tested, from Sentry. Brad Rydzewski, a senior vice president and general manager for Harness, said Codecov makes it simpler for DevOps teams to track testing coverage at a time when the volume of code being created in the age of artificial intelligence is exponentially increasing. Codecov is already widely used by enterprises and maintainers to automatically run tests on any code that for one reason or another was not tested earlier in the software development lifecycle (SDLC). Going forward, Harness plans to integrate the data that Codecov generates in real time with the Harness Software Delivery Knowledge Graph to provide deeper insights across DevSecOps workflows as AI agents are integrated into workflows. Ultimately, the goal is to automate testing as much as possible while maintaining separation of duties between AI agents that write code and AI agents that te...
Post a Comment
Read more

Latest OpenTofu Release Simplifies Configuration Updates

The latest update to the OpenTofu infrastructure-as-code (IaC) tool is making it simpler to update and refactor configurations without having to rework the entire codebase. Version 1.12.0 of OpenTofu has added a destroy = false lifecycle option that enables DevOps engineers to drop an object from state without issuing a destroy application programming interface (API) call. Previously, any time a resource was updated or added an API call would try to destroy the actual infrastructure behind it. While DevOps teams could work around that issue by carefully maintaining state, the chances that something could go awry were fairly high. Now OpenTofu 1.12.0 allows DevOps teams to tie prevent_destroy to an input variable within the same module. Once set to default, the API call to destroy the IT infrastructure environment is overwritten. That per-stack variable configuration means DevOps teams can define the safety behavior once per environment and have it stay consistent across every run. ...
Post a Comment
Read more

Why the Trust Layer Is the Next Thing Developers Will Commodify

Engineering roadmaps inside enterprises that never planned to build AI products are now being eaten by AI work. Teams at hospitals, banks and government agencies are spending huge chunks of their sprint capacity wiring up models, UI components and accessibility plumbing for AI features that aren’t core to what their business actually does. The mismatch between where the work is going and where the value is created is starting to force a different conversation about what belongs in-house and what doesn’t. Mike Hideo, VP of Software Engineering at TinyMCE, joins Mike Vizard to argue that the next layer developers will commodify is the AI trust layer — the governance, control, provenance and UI components that wrap every LLM-driven feature. The case is straightforward: writing a prompt is cheap, but building reliable audit trails, permission models and accessible interfaces around AI output is the part teams keep rebuilding from scratch with every new model release. The conversation g...
Post a Comment
Read more

Survey Surfaces Pervasive Adoption of AI Across SDLC

A global survey of 2,501 IT and DevOps professionals at organizations with more than 150 employees published today finds more than two-thirds (68%) work for organizations that have implemented artificial intelligence (AI) across some or all their software delivery workflows. Conducted by Tricentis, a provider of a platform for testing software, the survey identifies enhanced quality and risk detection (37%), enhanced accuracy and consistency (36%) and improved test automation coverage (32%) as the top benefits of integrating AI into those workflows Overall, 53% manage between six and ten AI or automation tools across their software development lifecycle (SDLC). However, the survey also finds that 60% admit their application developers also regularly ship untested code into production environments. David Colwell, vice president of AI and machine learning at Tricentis, said that as more AI-generated code is created, the volume of code that has not been tested is increasing, which in ...
Post a Comment
Read more

Microsoft Brings AI Agents Directly Into the Windows Terminal

Microsoft just shipped Intelligent Terminal 0.1 — an open-source, experimental fork of Windows Terminal with native agent integration built in. It’s available now from the Microsoft Store or via WinGet ( winget install Microsoft.IntelligentTerminal ), and it installs alongside your existing Windows Terminal without replacing it. This is an early release, clearly labeled as experimental. But it’s a meaningful signal about where Microsoft thinks the terminal is going. What it Actually Does The core idea is straightforward: Instead of copying an error message, opening a browser, hunting through Stack Overflow, and then jumping back to your shell, you stay in the terminal. An AI agent is right there, aware of what’s on your screen. Intelligent Terminal adds a persistent agent pane — a docked, context-aware panel where you can interact with an AI agent CLI without leaving your workflow. GitHub Copilot CLI is the default, but the architecture is open. Any Agent Client Pr...
Post a Comment
Read more