Conference50min
From vibe coding to harness engineering: modernizing a regulated environment with AI
AI-enabled migration of a banking mainframe to the cloud required a shift from “vibe coding” to “harness engineering.” The talk shows how to control AI-generated code in regulated environments through spec-driven development, evolutionary pipelines, and continuous validation, balancing agility, safety, and changing security rules.
talk.summaryAiDisclaimer
Anyul RivasGFT
talkDetail.whenAndWhere
Thursday, October 8, 09:30-10:20
TBA 4
talks.roomOccupancytalks.noOccupancyInfo
Migrating a banking mainframe to the cloud under fluctuating security regulations in three months seemed like an impossible mission. AI (agents, MCP tools) was the force multiplier that made it possible, but it demanded a paradigm shift. This session dissects the evolution from the illusion of vibe coding—generating code through fluid conversations—to the rigorous discipline of harness engineering.
When AI writes the code, software craftsmanship evolves. The focus is no longer on syntax, but on building safety nets. We will explore how to tame automated code generation in hostile and highly regulated environments by building relentless harnesses: Spec-Driven Development, evolutionary pipelines, and continuous validation.
Key Points
Evolution of Craftsmanship: The shift from typing code to orchestrating, limiting, and auditing systems generated by multiple sub-agents.
Harness Building: Using extreme testing (integration, test containers, environment simulation) to contain and certify the behavior of generated code.
Spec-Driven Development: The specification as a single, unbreakable contract between business, security, and AI agents.
Radical Pragmatism: How to maintain agility and design principles when the rules of the regulated environment change daily.
When AI writes the code, software craftsmanship evolves. The focus is no longer on syntax, but on building safety nets. We will explore how to tame automated code generation in hostile and highly regulated environments by building relentless harnesses: Spec-Driven Development, evolutionary pipelines, and continuous validation.
Key Points
Evolution of Craftsmanship: The shift from typing code to orchestrating, limiting, and auditing systems generated by multiple sub-agents.
Harness Building: Using extreme testing (integration, test containers, environment simulation) to contain and certify the behavior of generated code.
Spec-Driven Development: The specification as a single, unbreakable contract between business, security, and AI agents.
Radical Pragmatism: How to maintain agility and design principles when the rules of the regulated environment change daily.