News and Tech Update

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...

There is a particular flavour of engineering dysfunction that looks, from the outside, like peak performance. Deployments are frequent. Sprint velocity is high. The feature backlog is shrinking. Leadership is pleased. And underneath all of it, the system is quietly rotting. Technical debt compounds with every rushed deployment. Observability gaps widen because nobody has time to instrument the new services properly. The on-call rotation gets noisier every month. But the velocity metrics keep climbing, so nobody sounds the alarm until something breaks badly enough that velocity stops being the conversation. I call this the velocity trap, and it is the most common failure mode in engineering organizations that have adopted DevOps practices without internalizing DevOps principles. The practices say: automate, deploy frequently, iterate fast. The principles say: build quality in, create feedback loops, continuously learn and improve. When you execute the practices without the principles, ...

Anthropic has launched Claude Security in public beta for Claude Enterprise customers. The tool gives security teams a way to scan entire codebases for vulnerabilities — and generate targeted patches — without the usual back-and-forth that slows down remediation. It’s a meaningful step forward for teams struggling to keep pace with the growing volume and complexity of security threats. And it signals where AI-assisted development is heading next. From Research Preview to Public Beta Claude Security isn’t brand new. Anthropic first released it as Claude Code Security in February, initially limited to Enterprise and Team customers. Since then, hundreds of organizations have used it in production, surfacing vulnerabilities that existing tools had missed — in some cases, for years. That real-world feedback shaped what’s shipping today. The public beta is now open to all Claude Enterprise customers globally. Access for Team and Max plan users is coming soon. How it Wo...

I’m going to say something that will make every engineering manager uncomfortable: Stop asking your team to write documentation . Not because documentation doesn’t matter. It matters more than ever. But because asking humans to document their work after they’ve done it is a process that has failed consistently for thirty years, and no amount of “definition of done” checklists or documentation sprints is going to fix it. The people who know the most write the least. The docs that get written are stale within weeks. And the knowledge that matters most — the decisions, the gotchas, the “why” behind the code — rarely makes it into a document because it’s not the kind of thing you sit down and write. The Documentation Death Spiral I’ve watched this cycle play out on every team I’ve been part of: Week 1: “We need to document this.” Everyone agrees. Someone creates a Confluence space. Week 4: A few pages exist. They’re pretty good. Written by the one person who cares about docs. Week...

LocalStack today announced it has extended its ability to simulate Amazon Web Services (AWS) environments to provide an ability to debug applications before deploying them. Company CEO Colin Neagle said App Inspector makes it possible for developers to debug their applications running in a simulated AWS environment inside a container on a local server. Simulating the full application stack within a local sandbox container makes it possible to better understand application behavior such as data flows between AWS services, event execution paths and resource dependencies that may have been inadvertently misconfigured, noted Neagle. Once discovered, App Inspector then generates a visual representation of the interaction between services in the local environment to make it simpler to debug applications without digging through logs and then needing to upload a fix to a staging server running in the AWS cloud. That capability doesn’t replace the need for an observability platform but i...

The era of the “human-only” software engineer is rapidly receding into the rearview mirror. Google CEO Sundar Pichai revealed Wednesday that a whopping 75% of the company’s new code is now generated by artificial intelligence (AI), marking a major shift in how the tech giant builds its products. The velocity of this transition has caught even industry observers off guard. Just 18 months ago, in early 2024, AI-generated code accounted for only a quarter of Google’s output. By late 2025, that figure had climbed to 50%. Today’s 75% milestone signals that AI has moved from a supplemental “autocomplete” tool to the primary engine of production at Google. Pichai noted that the workflow has evolved into something “truly agentic.” Instead of human engineers laboriously writing lines of code or using AI to finish a single sentence, they are now supervising autonomous digital teams. These AI agents can plan, execute, and refactor entire codebases with minimal human intervention. The effic...