A developer reflects on lessons from Sandro Mancuso's 'The Software Craftsman', focusing on two key takeaways: radical ownership over your code (the 'mirror test' — asking what you could have done differently before blaming others) and how these principles shaped a practical hiring framework. When unexpectedly needing to hire for a fast-paced project, the author prioritized attitude over technical skills, looking for ownership mentality, comfort with ambiguity, a constructive approach to legacy code, and honesty about limitations. Specific interview questions used to surface these traits are shared, along with honest self-reflection on applying the craftsman mindset personally.

8m read timeFrom tnakov.dev
Post cover image
Table of contents
Stop Pointing FingersThe Mirror TestLegacy Code Is Not an ExcuseWhen I Had to Interview (Without Much Experience Doing It)What Mattered for a Fast-Paced ProjectThe Questions That HelpedIt WorkedApplying This to MyselfThe Book Is Worth Reading

Sort: