- Paperback: 208 pages
- Publisher: Addison-Wesley Professional; 1 edition (September 2, 2001)
- Language: English
- ISBN-10: 0201733862
- ISBN-13: 978-0201733860
- Product Dimensions: 7.4 x 0.6 x 9 inches
- Shipping Weight: 15.2 ounces (View shipping rates and policies)
- Average Customer Review: 4.1 out of 5 stars See all reviews (24 customer reviews)
- Amazon Best Sellers Rank: #967,439 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Software Craftsmanship: The New Imperative 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
From the Back Cover
By recognizing that software development is not a mechanical task, you can create better applications.
Todays software development projects are often based on the traditional software engineering model, which was created to develop large-scale defense projects. Projects that use this antiquated industrial model tend to take longer, promise more, and deliver less.
As the demand for software has exploded, the software engineering establishment has attempted to adapt to the changing times with short training programs that teach the syntax of coding languages. But writing code is no longer the hard part of development; the hard part is figuring out what to write. This kind of know-how demands a skilled craftsman, not someone who knows only how to pass a certification course.
Software Craftsmanship presents an alternative—a craft model that focuses on the people involved in commercial software development. This book illustrates that it is imperative to turn from the technology-for-its-own-sake model to one that is grounded in delivering value to customers. The author, Pete McBreen, presents a method to nurture mastery in the programmer, develop creative collaboration in small developer teams, and enhance communications with the customer. The end result—skilled developers who can create, extend, and enhance robust applications.
This book addresses the following topics, among others:
Software Craftsmanship is written for programmers who want to become exceptional at their craft and for the project manager who wants to hire them.
About the Author
Pete McBreen is an independent consultant who actually enjoys writing and delivering software. Despite spending a lot of time writing, teaching, and mentoring, he goes out of his way to ensure that he does hands-on coding on a live project every year. Pete specializes in finding creative solutions to the problems that software developers face. After many years of working on formal and informal process improvement initiatives, he took a sideways look at the problem and realized, “Software development is meant to be fun. If it isn’t, the process is wrong.” Pete lives in Cochrane, Alberta, Canada and has no plans to move back to a big city.
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
If you are looking for directions on how to become one of the software programing elite, this is the map. This book is also an excellent guide for those trying to staff software projects with quality talent in that you'll know who the true craftsmen really are. Perfectly edited, filled with solid references, clear examples, and easily readable text.
(1) Software Engineering, with it's focus on big-up-front design, is not working well in the business world.
(2) Emergent Design and Iterative Development actually work for business systems.
(3) An apprentice/journeyman/master system relying on communication and OJT will be more effective than a BS in CS and a one-week course in SQL.
(4) The focus on buzzwords and bleeding edge technologies is actually harmful to our craft.
(5) The idea that learning is somehow bad because it implies the learner doesn't know everything is bogus and wrong. In fact, the idea that there is a single 'right way to do it' is equally bogus. We should instead grow developers with a wide knowledge of different techniques and allow them to find the right technique for each project.
(6) The mobility and job-hopping of developers is counter-productive to effectiveness. People are not cogs. Therefore ...
(7) Developers who are widely successfull and stay at a company long enough be of real value should be highly compensated; the author suggests up to $250,000/year and that super-stars should be paid higher than the managers (and possibly executives) who they report to. Without this, ambitious developers are forced into becoming consultants, trainers, or managers.
---> That said, there were a few things that make this book less-than-five-stars:
(1) The work isn't really 'new.' The book is a neat combination of the work of Deming, DeMarco, Dave Thomas (The pragmatic programmer, not the Wendy's CEO), and the XP/Agile Crowd. A lot of the book is Deming applied to software, but readable and enjoyable.
(2) While some of the book is clearly ideas the author does consistently and knows work, some of it seems to be neat theoretical stuff that hasn't been tried. The thing that hit me was the ideas that developers should make $250,000 per year or they will be 'forced' into consulting ... the author is a consultant. How to even make it possible to create an environment where the developer makes more than his boss is worthy of a chapter or two, but it is not covered in depth, and I get the feeling that is because the author has never actually seen it in real life.
In short, if you have tried traditional charts and diagrams and design documents and big-test-plan 'Software Engineering' and you think 'there has got to be a better way' - try this book. If you are a big agile/XP/Scrum person looking for a book to give away to friends, this might be the one. If you are allready convinced and want more deep, practical guidance, you are probably better off going to the sources: Deming, DeMarco, Jeffries, Beck, Cunningham, Brooks, etc.
Most Recent Customer Reviews
In the [NATO 1969] report Peter Naur and Brian...Read more
It's time we admit that the so-called 'methodologies' don't work: they never have.Read more