Maintaining Engineering Craftsmanship When Speed Is the Primary Business Pressure

AI tools made building cheaper, faster, and more accessible than at any point in the history of software. They also made it easier to ship things nobody on the team understands, drown senior engineers in PR review, and mistake effortless agent output for good engineering. The business wants to move faster. The board wants to move faster. The tools enable it. The thing that appears to be standing in the way is engineering standards. This roundtable is for the leaders living that conversation, and trying to figure out which parts of craftsmanship are worth defending and which are worth letting go.

We will work through three failure modes that keep showing up in the field: the vibe-coding Ponzi scheme where AI-assisted teams accumulate technical debt they cannot see, review hell where senior engineers become full-time reviewers of AI-generated output they were not involved in creating, and the "easy is a smell" trap where teams confuse effortless agent output for competitive advantage. We will then discuss what craftsmanship actually means now that writing code by hand is no longer the bottleneck, and what leaders are doing in practice to hold the line: changing the workflow rather than just the tools, separating iteration speed from deployment cadence, and treating context engineering as a first-class engineering discipline. Participants will leave with concrete frameworks, honest stories from leaders navigating this in real organizations, and language they can take back to their own stakeholders when the next "ship it faster" conversation lands on their calendar.