News and Tech Update

Dynatrace announced Thursday it has agreed to acquire AI observability company Arize in a $915 million cash and stock transaction. Rick McConnell, CEO of Dynatrace, said the company expects demand for AI observability will keep growing as more AI systems move into production. He said acquiring Arize would speed up Dynatrace’s roadmap, expand its developer reach and bring Arize’s AI team into the company. Dynatrace said the deal would combine Arize’s AI evaluation and observability software with its own platform for correlating telemetry and tracing dependencies across applications, services and infrastructure. The transaction includes about $815 million in cash and replacement equity awards for Arize employees and is expected to close later this quarter or early in Dynatrace’s fiscal third quarter. DevOps teams are already used to piecing together telemetry across distributed systems when something breaks. AI adds another source of context to correlate when information about model ...

Most development teams don’t pick one AI model and stick with it anymore. They pick the best model for the job at hand and switch when the job changes. GitHub’s latest round of Copilot updates, published Aug. 13 in its weekly changelog covering the week of Aug. 10, reads like an admission that this is now normal — and that Copilot needs to be built around it rather than around any single model. The headline additions are two new models. Kimi K3 is rolling out across Copilot Pro, Pro+, Max, Business, and Enterprise plans. MAI-Code-1.1-Flash arrives alongside it, with native image understanding and what GitHub describes as improvements in coding quality, instruction-following, tool use, and performance. Neither replaces anything. They sit next to the models already available, which is the point. GitHub isn’t trying to win developers over to one model family. It’s trying to make sure whichever model they trust is one click away. That same logic shows up in Visual ...

Business automation often reaches production without the release discipline applied to application code. A routing rule changes, an approval threshold moves, or an integration starts writing to a new system. The edit may happen in a visual builder instead of a repository, but its blast radius is still real: orders can duplicate, customers can receive the wrong message, and operators can lose the context needed to recover. The useful shift is to treat every workflow change as a deployment. That does not mean forcing a full software delivery platform onto every automation tool. It means defining a small release contract before the new behavior touches live work. Define the Deployable Unit A workflow is larger than its diagram. Its deployable unit includes decision rules, field mappings, credentials, schedules, permissions, retry behavior, operator screens, and every external side effect. If a change affects any of those elements, the release record should name them explicitly. Give t...

Developers are often assumed to resist AI because they fear it will take their job , that using it means training their own replacement. That is not quite right. What is happening is that AI has changed, permanently, what the job of a developer is. And not every developer is, or has to be, okay with that. A 2024 peer-reviewed study backs this up: developers’ concerns centre less on job loss and more on how AI reshapes the work itself. The market data agrees. In 2025, 84 percent of developers were using or planning to use AI coding tools, yet only 33 percent trusted the code those tools produce, according to the same survey . Adoption is rising. Trust is falling. That gap is the real signal, and it has nothing to do with job security. Traditional coding is hands-on. Developers solve problems, shape architecture, write code, debug, and make technical decisions directly. That is the part most engineers enjoy. AI-assisted coding moves the developer up a level: instructing, reviewin...

ProjectDiscovery has made available an autonomous security testing platform that leverages an open source artificial intelligence (AI) testing framework to detect and validate vulnerabilities at a lower total cost. Company CEO Rishi Sharma said version 1.0 of the Neo platform is also available via a cloud service that makes it possible for DevSecOps teams to run tests and conduct investigations using a consumption-based pricing model. Additionally, Neo 1.0 adds integrations with DevOps tools and platforms such as GitHub, Jira, Confluence, Slack, Linear, application programming interfaces (APIs), webhooks, and the Model Context Protocol (MCP). Based on an open source project, ProjectDiscovery, in addition to using Neo to detect, validate and route vulnerabilities to the responsible developer, also provides access to Nuclei, an open-source vulnerability scanner driven by customizable YAML templates to detect misconfigurations and exploits. Also included are tools such as Subfinder fo...

Every enterprise deployment conversation eventually comes down to the same question: Which strategy is right for this release? Most teams answer it by reaching for whatever approach they used last time. That is not a strategy; it is a habit, and habits developed for one deployment context carry real risk when applied uncritically to a different one. The deployment strategy decision matters more than most teams give it credit for. Get it right and releases become routine — predictable, reversible and low-drama. Get it wrong and a deployment that should have been straightforward becomes a Friday afternoon incident investigation. This guide walks through the four most widely used software deployment strategies, identifies the scenarios each handles best and provides a decision framework for matching the right approach to the right situation. The Four Strategies and What They Are Actually For Before getting into scenarios, it helps to be precise about what each strategy does and does...