Software Craftsmanship is a call to arms for programmers: an impassioned manifesto that restores the developer to a central role in large-scale projects, and shows developers how to master the skills they need to succeed in that role. Software Craftsmanship transcends "software engineering," demonstrating that quality software can't simply be "manufactured": it must be built by craftspeople with pride in their work, and a personal commitment to excellence. KEY TOPICS: In Software Craftsmanship , Pete McBreen focuses on the craft of software development, explaining why current "software engineering" techniques often fail, and offering programmers a new path to excellence. Just as the modern carpenter benefits from better tools, materials, and understanding, the modern programmer can benefit from better computers, reusable components, and more robust languages -- but only if he or she is prepared to treat the software profession as a true "craft." McBreen explains what software "craftsmanship" means, how its affects users, and how it changes the developer's relationship with customers. He introduces the concepts of software apprentices and journeymen, shows what can (and can't) be learned from the software engineering movement, and presents specific steps you can take now to move towards craftsmanship in your work -- and your organization. MARKET: For all programmers, software engineers, application developers who want to gain greater personal satisfaction from their work, and for project managers who want to lead more successful projects while building great teams and retaining great developers.

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 alternativea 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 resultskilled developers who can create, extend, and enhance robust applications. This book addresses the following topics, among others: Understanding customer requirements Identifying when a project may go off track Selecting software craftsmen for a particular project Designing goals for application development Managing software craftsmen

Autorentext
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.

0201733862AB07092002

Klappentext

• Putting the "people" back into software development: why "software engineering" isn't enough.
• Transforming the developer's relationship with users and customers.

• Specific steps you can take today -- as a developer or project manager. Software Craftsmanship is a call to arms for programmers: an impassioned manifesto that restores the developer to a central role in large-scale projects, and shows developers how to master the skills they need to succeed in that role. Software Craftsmanship transcends "software engineering," demonstrating that quality software can't simply be "manufactured": it must be built by craftspeople with pride in their work, and a personal commitment to excellence. In Software Craftsmanship, Pete McBreen focuses on the craft of software development, explaining why current "software engineering" techniques often fail, and offering programmers a new path to excellence. Just as the modern carpenter benefits from better tools, materials, and understanding, the modern programmer can benefit from better computers, reusable components, and more robust languages -- but only if he or she is prepared to treat the software profession as a true "craft." McBreen explains what software "craftsmanship" means, how its affects users, and how it changes the developer's relationship with customers. He introduces the concepts of software apprentices and journeymen, shows what can (and can't) be learned from the software engineering movement, and presents specific steps you can take now to move towards craftsmanship in your work -- and your organization. Pete McBreen has successfully used and taught object-oriented techniques since 1989. He has designed and taught O-O courses for clients such as Nortel, CDC, and the University of Calgary. He is a frequent speaker at TOOLS, OOPSLA, and other advanced developer's conferences.

  Inhalt

  Preface.

  I. QUESTIONING SOFTWARE ENGINEERING.

  1. Understanding Software Engineering.

  The Paradox of Software Engineering.

  The Modern Definition of Software Engineering.

  Is Software Engineering a Good Choice for Your Project? 2. The Problems with Software Engineering.

  Can Software Development Be Made Systematic and Quantified?

  The Hazards of the Good Enough Software Approach.

  What Is the Alternative to Software Engineering? 3. Understanding Software Development.

  Software as Capital.

  Does the Division of Labor Work for Software Development?

  One Size Does Not Fit All. 4. Finding a Better Metaphor Than Software Engineering.

  Finding a Better Metaphor Than Software Engineering.

  The Craft of Software Development.

  Parallels with Traditional Craftsmanship.

  The Resurgence of the Craft of Software Development. II. SOFTWARE CRAFTSMANSHIP.

  5. Putting People Back into Software Development.

  Craftsmanship Is About Getting Better at Software Development.

  Craftsmanship Encourages Developers to Write Great Software.

  A Call to Arms. 6. Craftsmanship Is the Opposite of Licensing.

  Craftsmanship Is Personal.

  Licensing Is an Illusion.

  Craftsmanship Focuses on the Individual. III. IMPLICATIONS OF SOFTWARE CRAFTSMANSHIP.

  7. How Craftsmanship Affects the Users of Systems.

  Software Craftsmanship Works Because Software Is Easy to Copy.

  Craftsmen Have a Different Relationship with Their Users.

  Great Software Deserves to Be Signed.

  Craftsmen Need Demanding Users.

  Software Craftsmanship Leads to Collaborative Development. 8. Customers Have a Different Relationship with Craftsmen.

  Setting Realistic Delivery Dates.

  Exposing the Fallacy of Good Enough Software.

  Allowing Software Craftsmen to Take Credit for Their Work.

  Start Exploiting the Difference in Productivity Between Developers.

  But How Do We Know How Good a Developer Really Is?

  Customers Make a Cost/Quality Trade-off When Choosing Craftsmen.

  Customers Have Long Term Relationships with Software Craftsme…