The Human Side of Software Craftsmanship: Conversations with Dan Nort…

Between 2011 and 2014, through UGtastic, I had the privilege of conducting and recording over 200 high-bandwidth conversations with the practitioners who shaped modern software development.

Looking back at our restored interview archive, two conversations stand out as foundational milestones for understanding the true ethos of our industry: my interviews with Dan North (creator of Behavior-Driven Development) and Sandro Mancuso (author of The Software Craftsman and founder of the London Software Craftsmanship Community).

Today, software engineering discussions are often dominated by metrics: test coverage percentages, CI/CD pipeline runtimes, and pull request cycle times.

Listening to Dan North and Sandro Mancuso reminds us of a truth that is too easily forgotten: Software Craftsmanship was never about dogmatic rules or vanity metrics. It was about human dignity, psychological safety, and professional pride.

Dan North on BDD: TDD Was About Communication, Not Testing

When Dan North introduced Behavior-Driven Development (BDD) and tools like JBehave and Cucumber, the industry was caught in a bitter debate over Test-Driven Development. Developers were arguing about mocking frameworks, class isolation, and test suite execution speed.

In our conversation (read the Dan North archive interview), Dan articulated the core breakthrough:

“BDD isn’t about testing your code. BDD is about creating a shared language so that business analysts, product managers, and developers are talking about the exact same system behavior.”

Dan pointed out that when engineers write tests using domain behavior statements (“Given an active account, When user submits an order, Then charge ledger”), tests stop being an adversarial verification chore. They become an executable, living specification that bridges the communication gap between humans.

Sandro Mancuso on the Craft Manifesto: Raising the Bar of Developer Dignity

At Software Craftsmanship North America (SCNA) in Chicago, Sandro Mancuso laid out the philosophical foundation behind the Software Craftsmanship movement (read the Sandro Mancuso interview).

The Agile Manifesto had succeeded in making software delivery iterative, but in many enterprises, “Agile” had been reduced to two-week Jira sprints and endless standup meetings without any regard for technical quality.

Sandro explained why the Craftsmanship movement emerged:

Not only working software, but well-crafted software: Code that is readable, modular, and easy to change.
Not only responding to change, but steadily adding value: Refactoring continually so the codebase does not rot under deadline pressure.
Not only individuals and interactions, but a community of professionals: Creating peer apprenticeships, katas, and local user groups where senior engineers mentor the next generation.

Sandro emphasized that craftsmanship is not about perfectionism for its own sake. It is about professional self-respect: taking pride in delivering systems that do not wake your teammates up at 3:00 AM.

💡 Why the Human Signal Matters More in the AI Era

In 2026, as AI tools generate thousands of lines of syntax in seconds, the insights of Dan North and Sandro Mancuso are more relevant than ever:

Syntax is cheap; shared understanding is rare: An LLM can generate boilerplate, but it cannot negotiate business domain intent with stakeholders. That requires human empathy and BDD-style behavioral clarity.
Craft is an act of care: High test coverage generated by an automated bot does not equal good architecture. Clean seams, bounded contexts, and maintainable systems require human judgment.
Mentorship is the lifeblood of our craft: We do not learn how to be great engineers from manuals alone; we learn by pairing with experienced practitioners who model how to think through complex trade-offs with humility and care.

In Part 4, we will examine the intersection of security and architecture: exploring static AST analysis lessons from Justin Collins and RailsConf 2014.