Author: Mike Vizard

  • Making the Case for AI in Testing, Security and Delivery—Not Just Coding

    Making the Case for AI in Testing, Security and Delivery—Not Just Coding

    Harness CEO and co-founder Jyoti Bansal unpacks a core challenge facing modern software teams: while AI is dramatically increasing the amount of code being written, it is also putting unprecedented pressure on everything that happens after code is committed.

    Bansal argues that much of the industry’s AI focus has centered on the developer inner loop—AI-assisted coding on laptops—while overlooking the outer loop, where most of the real work lives. Testing, security scanning, deployment verification, compliance checks, release orchestration, and cost management consume the majority of engineering effort in large organizations. As AI accelerates code generation, those downstream processes become bottlenecks unless they are equally automated and modernized.

    This is where Bansal frames Harness’ vision of “AI for everything after code.” Rather than relying on generic copilots, he describes an approach built around purpose-designed AI agents that handle specific DevOps, testing, security, and FinOps tasks. These agents operate with deep contextual awareness, drawing from a software delivery lifecycle knowledge graph that reflects an organization’s infrastructure, policies, pipelines, and operational constraints.

    Crucially, Bansal emphasizes that AI should not replace human judgment in production environments. Instead, AI is used to generate deterministic, auditable orchestration—pipelines, tests, rollout strategies, and safeguards—that humans can review, approve, and govern. This human-in-the-loop model is especially important for large and regulated enterprises, where reliability, security, and blast-radius control matter as much as speed.

    They also explore how rising code volumes—especially from AI-generated code—can actually reduce delivery throughput and quality if the outer loop is neglected. Without strong automation, observability, and guardrails, more code simply means more vulnerabilities, more failures, and more rework.

    The message is clear: AI’s real impact on DevOps will be determined not by how fast teams write code, but by how intelligently they automate, secure, and govern everything that comes next.

  • How Low-Code Is Reshaping DevOps Automation and Governance

    How Low-Code Is Reshaping DevOps Automation and Governance

    Jon Scolamiero breaks down how low-code platforms are becoming an increasingly important part of the modern DevOps ecosystem. As organizations grapple with rapid shifts brought on by AI, vibe-coding practices, and an explosion of tooling, Scolamiero argues that low-code isn’t a shortcut—it’s a way to bring structure, automation, and transparency back into software delivery.

    He explains that the core mechanics of DevOps don’t disappear in a low-code environment. Pipelines still need to deploy reliably, infrastructure still needs to be provisioned, and applications still need to be secured and monitored. What changes is how teams interact with those systems. Low-code abstracts much of the repetitive orchestration work so teams can focus on governance, quality, and outcomes instead of plumbing. For organizations struggling with shadow AI, fragmented workflows, or inconsistent platform engineering practices, this abstraction can be the difference between chaos and clarity.

    Scolamiero also touches on the growing divide between U.S. and EU compliance expectations. While the EU pushes ahead with strong regulatory frameworks—including around AI transparency—the U.S. market often lags in political will but compensates with heavier requirements in highly regulated industries like federal, defense, and finance. That gap puts new pressure on DevOps teams to understand not just how software is built, but how every dependency enters the environment. Software supply chain security, Scolamiero notes, is no longer a niche concern—it’s a foundational requirement.

    Looking ahead, he warns that AI-driven development may soon trigger a high-profile security incident unless organizations adopt responsible governance practices. For DevOps teams, the message is clear: abstraction and automation are powerful, but only if paired with visibility, policy, and a strong understanding of the end-to-end delivery chain.