The integration of artificial intelligence into software development is doing more than just accelerating production; it is acting as a litmus test for professional identity. Historically, developers who viewed coding as a meticulous craft and those who viewed it as a means to an end were indistinguishable in the workplace. They occupied the same offices and followed identical workflows. Because the manual labor of writing syntax was mandatory for everyone, the underlying philosophy of the developer remained obscured by the shared necessity of the grind.

Simon Willison (developer and researcher) highlights a perspective from Les Orchard suggesting that AI-assisted programming has introduced a definitive fork in the road. On one side, developers are embracing the role of a director, steering models and autonomous agents to generate logic while focusing on high-level architecture. On the other, craft-lovers continue to insist on hand-crafting code, valuing the intrinsic process of manual creation. This divergence isn’t just about productivity; it is an existential shift that reveals the core motivation behind why individuals entered the field.

This AI split suggests that the future of engineering management will require navigating these two distinct mentalities within a single team. While automated tools offer speed, the tension between efficiency and craftsmanship could reshape team dynamics and the definition of seniority. As the make-it-go camp accelerates output through machine direction, the industry must decide how it values the traditional craft of programming in an era of ubiquitous automation.

The integration of artificial intelligence into software development is doing more than just accelerating production; it is acting as a litmus test for professional identity. Historically, developers who viewed coding as a meticulous craft and those who viewed it as a means to an end were indistinguishable in the workplace. They occupied the same offices and followed identical workflows. Because the manual labor of writing syntax was mandatory for everyone, the underlying philosophy of the developer remained obscured by the shared necessity of the grind.

Simon Willison (developer and researcher) highlights a perspective from Les Orchard suggesting that AI-assisted programming has introduced a definitive fork in the road. On one side, developers are embracing the role of a director, steering models and autonomous agents to generate logic while focusing on high-level architecture. On the other, craft-lovers continue to insist on hand-crafting code, valuing the intrinsic process of manual creation. This divergence isn’t just about productivity; it is an existential shift that reveals the core motivation behind why individuals entered the field.

This AI split suggests that the future of engineering management will require navigating these two distinct mentalities within a single team. While automated tools offer speed, the tension between efficiency and craftsmanship could reshape team dynamics and the definition of seniority. As the make-it-go camp accelerates output through machine direction, the industry must decide how it values the traditional craft of programming in an era of ubiquitous automation.