{"id":3241,"date":"2026-03-06T11:25:00","date_gmt":"2026-03-06T10:25:00","guid":{"rendered":"https:\/\/craft.tasnadi.group\/?p=3241"},"modified":"2026-09-04T11:40:08","modified_gmt":"2026-09-04T09:40:08","slug":"craft-2026-engineering-in-the-exponential-ai-era","status":"publish","type":"post","link":"https:\/\/craft-conf.com\/2027\/blog\/craft-2026-engineering-in-the-exponential-ai-era\/","title":{"rendered":"Craft 2026: Engineering in the Exponential AI Era"},"content":{"rendered":"\n

The shift in software engineering isn\u2019t linear \u2013 it\u2019s exponential. AI is no longer an experimental tool at the edge of the development workflow. It is actively reshaping how engineers write code, design systems, structure teams, and think about their careers. This year at Craft<\/a>, we are not asking whether AI will change software engineering. That transformation is already underway. The real question is: how do we adapt intentionally and effectively?<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Because this is one of those rare moments in the industry when the often-repeated phrase \u201cthose who stay out will fall behind\u201d<\/em> stops being a clich\u00e9 and becomes reality. Many engineers already feel the pressure of keeping up, and the pace shows no signs of slowing down. New models, new agent frameworks, new evaluation methods, and new architectural implications appear almost weekly. Those who invest in understanding these changes will accelerate. Those who don\u2019t may find the gap widening faster than expected.<\/p>\n\n\n\n

Craft Conference 2026<\/a> is designed around this inflection point.<\/strong><\/p>\n\n\n\n

AI-Native Software Engineering: When AI Is Not a Tool, but a Teammate<\/strong><\/h2>\n\n\n\n

At the heart of the conference is its largest thematic pillar: AI-native software engineering<\/strong>.<\/p>\n\n\n\n

AI-native development means designing software, workflows, and teams with the assumption that AI is part of the default environment. It\u2019s no longer about occasionally asking an AI assistant for help. Instead, it means building development processes where AI actively participates in coding, reviewing, testing, and even architectural exploration.<\/p>\n\n\n\n

Engineers from companies such as Anthropic, NVIDIA, Meta, Amazon Web Services, and IBM will share how their teams are adapting workflows, code review practices, and system design principles to this new reality.<\/p>\n\n\n\n

From Anthropic\u2019s Claude Code team, Kashyap Murali<\/strong> presents two highly anticipated talks. One focuses on making AI coding agents trustworthy \u2013 a crucial challenge as teams increasingly rely on AI-generated code. The other explores one of the fastest-emerging disciplines in AI development: evaluating and improving the reliability of AI-driven engineering workflows.<\/p>\n\n\n\n

At NVIDIA, Aaron Erickson<\/strong> addresses one of the industry\u2019s most complex technical challenges: how to combine deterministic software systems with probabilistic AI models in production environments.<\/p>\n\n\n\n

From Meta, Ian Thomas<\/strong> explores what it truly means for entire engineering teams to become AI-native \u2013 not just more productive, but fundamentally different in how they collaborate with intelligent systems.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Architecture, Platforms, and the Human Factor<\/strong><\/h2>\n\n\n\n

As AI accelerates coding, architecture becomes even more important<\/strong>.<\/p>\n\n\n\n

A well-structured system enables AI tools to be effective. Poor architecture, on the other hand, can make AI-generated outputs confusing, inconsistent, or even unsafe.<\/p>\n\n\n\n

Experts such as Gregor Hohpe<\/strong>, Neal Ford<\/strong>, and Mark Richards<\/strong> will explore how software architecture needs to evolve for AI-driven systems and rapidly accelerating development cycles.<\/p>\n\n\n\n

Michael Feathers<\/strong> will address another critical challenge: legacy systems. His talk explores why healthy codebases are the first step toward becoming truly AI-ready. Without maintainable foundations, AI can amplify complexity instead of reducing it.<\/p>\n\n\n\n

But Craft also focuses on the human side of these transformations<\/strong>.<\/p>\n\n\n\n

Rapid technological change inevitably creates stress, uncertainty, and pressure for engineers and organizations. Talks on mindset, cognitive bias, and team psychology examine how developers and leaders can navigate these challenges.<\/p>\n\n\n\n

Michelle Brush<\/strong> from Google explains the Jevons paradox in the context of AI: when automation makes certain tasks easier, the remaining problems often become significantly harder.<\/p>\n\n\n\n

Meanwhile, Sander Hoogendoorn<\/strong> describes what he calls the exponential era<\/em> \u2013 a time when technological change accelerates so rapidly that standing still effectively means falling behind.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Guiding Through Change: Voices That Shaped the Industry<\/strong><\/h2>\n\n\n\n

Craft 2026<\/a> also brings together some of the most influential thinkers in modern software engineering.<\/p>\n\n\n\n