Foreword
This book asks some tough questions.
Is software engineering appropriate for projects of less than 100 developer-years? Is the specialization inherent in software engineering a good idea? Can software development even be expressed in engineering terms?
It also asks some sensitive ones: Are less experienced developers paid too much, and should senior developers be paid more than almost anyone else in their organization? Should tools that are less than ten years old be used on long-term projects?
And at its heart, this book asks the big question: How can we reorganize the process of building software so that it works?
The book has some controversial answers: It suggests that we've lost sight of a simple truth—large methodologies and formal ...
Get Software Craftsmanship: The New Imperative now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
