After the Gold Rush: Creating a True Profession of Software Engineering

If we truly are an Engineering profession, why haven't we adopted the kinds of process and quality control measures demanded of other Engineering professions, like electrical engineering, mechanical engineering, etc? The answer is maturity.After working in software for 13 years, I have seen my share of late deadlines, heroic efforts which 'save the day' on a project, weeks worth of code thrown out in favor of another few week rewrite, the list goes on... When was the last time you saw a contractor rip down a building after it was 70% done because they decided the 'basement wasn't good enough'? It happens all the time in software.With some of the observations this author bases his conclusions on, it felt as if he has worked beside me for years. I don't agree with everything he has to say, but it is compelling and thought provoking in the extreme.If you have seen projects that routinely go over budget, routinely require heroic efforts, routinely seem to lack requirements, and think 'there must be a better way', then read this book. It took me less than a week of evenings, and it has already become the best thing I've done to create a 'vector of change' within my organization towards better Engineering practices. It's time we all grow up, and act like the real engineers we are.

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.

I've been in this business since March 1982. I've read them all. This is the BEST book you can read on the subject. I know, you get these books, try to read the first chapter, they're poorly written, boring, and grow dust on your shelf. THIS BOOK IS NOT LIKE THAT! If you read ANY book on software process and the problems currently faced by software professionals, this is it! And, in response to "A reader from Deep in the trenches of software development", grow up! Hopefully, dinosaurs like you will die out, just the way Ptolemaic theory died when Copernican theory was adopted. It's unfortunate that the code-and-fix mental disease persists, mostly in the minds of "heroes, ball-hogs, and silver-bullet all-nighter 24/7" infected programmers. I, personally, went to the University of Michigan College of Engineering, and have a degree called "Computer Engineering". The software field requires all practitioners to elevate themselves to Engineers. One would never dig the foundation for a huge structure without first having solid requirements, design review, blueprints, and permits. The current software field still goes right to digging. The software engineering portion of our profession is the most important: get those requirements, get buy-in, do a design, get it approved. Then, once you're done with that, you can get a programmer to code it! Those of you out there that still do not believe in software process enabling you to meet your goals better than the retched code-and-fix mentality, I ask that you follow leaders with a process and examine the results, or do the rest of us a favor and leave the field.

Another great book in a line of great books from Steve McConnell that puts together a compelling case that it's time for us software developers and the profession as a whole to grow up! This book, starting with the title itself, offers good insight on where the profession is and where it really needs to go. It's a quick read relative to some of Steve's other books (Code Complete, Rapid Development), but still gives good coverage of his premise and a convincing case. Like Code Complete and Rapid Development, this is an important book for any developer/leader who is serious about the profession.

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