Software craftsmanship is a movement that treats software development as a craft: software must not only work, it must be well designed, readable and easy to evolve. It was formalized in a manifesto published in 2009, which extends the Agile Manifesto.
In practice, it relies on demanding technical practices:
- automated tests and TDD;
- code review and pair programming;
- continuous refactoring and design principles (SOLID, clean code);
- knowledge sharing and mentoring between developers.
Agile organizes how a team delivers, craftsmanship deals with how code is written. The two complement each other: without technical quality, an agile team ends up slowed down by its debt.
Why it matters when hiring
A candidate who claims to follow craftsmanship should be able to prove it in their code: tests, structure, commit history, reviews. In interviews, a refactoring or code review exercise says far more than a discussion of principles. The opposite trap exists too: a profile who polishes endlessly and forgets the deadline.
