After the Gold Rush: Creating a True Profession of Software Engineering (Best Practices) (Paperback)

by Steve McConnell (Author) "In 1975, Fred Brooks compared the development of large software systems to dinosaurs, woolly mammoths, and saber-toothed tigers fighting the glutinous grip of the tar..." (more)
Key Phrases: programming heroes, software engineering body, software engineering code, United States, Computer Society, Fundamentals of Engineering (more...)

Editorial Reviews

Amazon.com Review
Software developers are supposed to work insane hours, drink only caffeinated beverages, and have no personal lives, all in the interest of shipping the all-important Product. In the popular consciousness, the desperate programming team has acquired a status similar to that of the movie protagonist drinking whiskey alone at a bar--both are examples of ritual self-abuse deemed heroic. In After the Gold Rush: Creating a True Profession of Software Engineering, Steve McConnell argues that the methodical abuse of programmers causes bad code, unhappy people, and reduced profitability in the long run. In place of the existing system of crazy deadlines, clueless marketing, and scattershot programming strategies, McConnell proposes making software engineering into a "true profession." Such a profession would have a well-defined body of core knowledge, a system of professional certifications, and a code of professional ethics.

The question of whether such a "professionalization" of software development is a good idea is up for debate, certainly. It seems that a lot of programming jobs involve standard problems and solutions, which would lend themselves to teaching and testing. On the other hand, quantum-leap innovation has often come from "cowboy" artisans who deviate from the standard practices. Similarly, aggressive technology investors aren't interested in deliberate, standardized work--they want world-beating products (and they want them to market immediately, if not sooner). After the Gold Rush makes a well-reasoned, well-supported argument for a more structured programming profession, and is worthwhile reading for any technology executive or project manager. --David Wall

Topics covered: The problem with "code-and-fix" software development, the elusive nature of a body of knowledge in high-tech subjects, the structure of more traditional engineering professions (civil, chemical, and others), solution design versus implementation, and suggestions for how software engineering professionals might get trained and certified.

Product Description
In this newest addition to Microsoft Press's acclaimed BEST PRACTICES series, award-winning author Steve McConnell offers candid reflections upon and a look ahead at the software engineering profession from one of the industry's most highly regarded practitioners. AFTER THE GOLD RUSH is a collection of illuminating original essays on contemporary software development topics that highlight critical trends and call for a more rigorous and standards-based profession. McConnell delivers a lively and provocative narrative that aims to help software developers step back from the day-to-day rush of their work and think about where their careers-and the industry they're helping to shape-are going.

Product Details

• Paperback: 182 pages
• Publisher: Microsoft Pr (November 1999)
• Language: English
• ISBN-10: 0735608776
• ISBN-13: 978-0735608771
• Product Dimensions: 9 x 7.3 x 0.7 inches
• Shipping Weight: 12.8 ounces
• Average Customer Review: 3.6 out of 5 stars See all reviews (42 customer reviews)
• Amazon.com Sales Rank: #659,208 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

69 of 71 people found the following review helpful:

5.0 out of 5 stars Concise excellence, November 5, 1999

By	Robert Lawrence (Brooklyn, NY USA) - See all my reviews

Steve McConnell comes through again. In this short collection of essays, he argues convincingly that the software industry can and must change drastically. The industry's "code-and-fix" practices, which have over and over proved ineffective and even dangerous, have to go. The image of the heroic programming genius, saving the dysfunctional organization over and over from behind a wall of empty pizza boxes and soda cans, must go as well. Empty and foolish heroism must be replaced by good processes, patient planning, and good engineering practice.

McConnell argues that in order for this change to occur, a proper "profession" of software engineering must be created. Such a profession would, above all, aid the diffusion of effective software engineering practices. In addition, a profession backed by universities, professional guilds, and a system of certification would make developers accountable for the software they create, and would allow them to take a stand against clueless management who want systems "done yesterday"--whatever the ultimate cost or detrimental effect on quality.

My only complaint is that McConnell ignores one important factor in software: the impatience of contemporary investors and financial professionals. The short-term focus of these parties is hurting quality in every industry, including software. Perhaps the only way new companies will be able to battle their influence will be to remain private--a difficult sacrifice that will require character verging on stubbornness.

For an interesting pairing, you may want to read this book alongside Mark Minasi's "The Software Conspriracy."

35 of 39 people found the following review helpful:

5.0 out of 5 stars An excellent roadmap and an important book, May 17, 2000

By	Daniel Read "Software Developer" (Atlanta, GA USA) - See all my reviews (REAL NAME)

Steve McConnel is right on the money here. Software Engineering needs to mature into a real "profession", in the sense the engineers, doctors, and lawyers belong to a "profession". This is the basic point of the book. As McConnell says in the Introduction, "It's time for software development to grow up."

However, contrary to some other reviews, this book is a lot more that just a rehash of "Rapid Development" (one of McConnell's earlier books, and an essential book in its own right). "After the Gold Rush" does make some points that are also made in "Rapid Development", but the intent and content of "After the Gold Rush" is totally different.

This book is part manifesto, and part roadmap. McConnell puts forth the idea that, despite the proven effectiveness of many fully developed "best practices", the software development industry as a whole continues to ignore them and engage in "code and fix" style development. The software industry, McConnell writes, needs to grow up and start taking on some of the characteristics of more mature professions, especially the engineering profession. After making this point, and backing it up with studies and other empirical data, McConnell proceeds to lay out the qualities that a mature profession possesses, which of those qualities the software industry is lacking, and how we can move forward toward maturity, examining such topics as education, licensing, and ethics.

I feel this is essential reading for any developer. Will this book teach you about coupling and cohesion or show you the ins and outs of running a JAD session? No, that's what "Code Complete" and "Rapid Development" are for (and please read those if you haven't). This book foretells (and I believe will help fulfill) the inevitable future of software engineering as a profession. This book provides a look at what software developers do from a higher perspective, and puts the profession in a broader (even historical) context. It has helped me to consider my job as a software developer from a fresh angle, and to take stock of my role in the future of the profession.

22 of 24 people found the following review helpful:

4.0 out of 5 stars Good summary of ongoing evolution of the software profession, April 25, 2000

By	David Stengle (Princeton, NJ USA) - See all my reviews (REAL NAME)

Mr. McConnell's latest book delivers a pitch for certification in software engineering. He makes a reasoned case and provides a little useful historical context. Unlike his other books (Code Complete, Rapid Application Development, and Software Project Survival Guide), this book offers little of direct use to a practitioner. The book aims to accelerate a coming trend, rather than inform its readers about what exists today.

If you are at SW-CMM level zero (never heard of CMM) or level minus one (think it's nonsense), then this may present new concepts - but I found this book to focus on the process of certification and credentials rather than the software process itself.

I found the chapter on professional ethics to be rather humorous, although I doubt this was the author's intention. Look at the miniscule number of doctors or lawyers that lose certification. In practice, professional certification is used to defend established players from newcomers, particularly foreign newcomers. This will be a big issue given the large number of first-generation immigrants making huge contributions to software in North America. I think in this area, as well as the discussion on the "Chasm" (see Geoffrey Moore) in adopting practices, the author could take a stab at some conclusions, however speculative.

As always, Mr. McConnell's crisp writing style and deep industry knowledge make for a pleasant, informative read; however, I think only people working on setting policy, establishing certification or a defining a curriculum will find the material concretely helpful.