Have one to sell? Sell yours here
After the Gold Rush: Essays on the Profession of Software Engineering (Best Practices)
 
 
Tell the Publisher!
I’d like to read this book on Kindle

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

After the Gold Rush: Essays on the Profession of Software Engineering (Best Practices) [Paperback]

S. McConnell
3.2 out of 5 stars  See all reviews (4 customer reviews)

Available from these sellers.


Amazon.co.uk Trade-In Store
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Plus, get an extra £5 Gift Certificate when you trade in books worth £10 or more before June 30, 2012. Visit the Books Trade-In Store for more details.

Product details

  • Paperback: 208 pages
  • Publisher: Microsoft Press,U.S. (1 Nov 1999)
  • Language English
  • ISBN-10: 0735608776
  • ISBN-13: 978-0735608771
  • Product Dimensions: 23.1 x 18.8 x 1.8 cm
  • Average Customer Review: 3.2 out of 5 stars  See all reviews (4 customer reviews)
  • Amazon Bestsellers Rank: 1,412,505 in Books (See Top 100 in Books)

More About the Author

Steve McConnell
Discover books, learn about writers, and more.

Visit Amazon's Steve McConnell Page

Product Description

Amazon.co.uk 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 "professionalisation" 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, standardised 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.

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 be trained and certified. --David Wall

Product Description

Lively and highly readable introspections on the software development industry appeals to both insiders and non-technical readers alike with candid reflections takes a look at the future of software engineering as a profession. McConnell, a best-selling and award-winning author, describes software development practices and trends, provides valuable insight, and gives the non-technical public an understanding of software engineering.

Inside This Book (Learn More)
First Sentence
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 pit. Read the first page
Explore More
Concordance
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Tag this product

 (What's this?)
Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items.
Your tags: Add your first tag
 

Sell a Digital Version of This Book in the Kindle Store

If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store. Learn more

Customer Reviews

Most Helpful Customer Reviews
1 of 1 people found the following review helpful
By A Customer
Format:Paperback
A quick and easy read. Whilst I agree with much of what the book says, I don't think it's anything brilliant as far as being a book goes - no amazing revelations to improve your development.

Basically, it says current software development is pants (no surprises there) because, although we know how software should be developed, we don't actually apply that knowledge in real life, ending up stuck in a rut with code-and-fix development. McConnell argues that for improvement we need to adopt an "engineering" approach, which ultimately will require certification and/or professional licensing of developers. He believes this should filter out the waste-of-space developers, leaving folk who know what they are doing.

Worthwhile reading, and all good advice, but no amazing insights that I hadn't heard before. I'd rate it at 3.5 stars.

Comment | 
Was this review helpful to you?
By Jennifers Daddy TOP 1000 REVIEWER
Format:Paperback|Amazon Verified Purchase
I bought this after I had already read Code Complete2, Rapid Development and Professional Software Development. It was harder to get into (and is older) so would now avoid and go for one (or all) of those titles I mentioned, as they are all superb.
Comment | 
Was this review helpful to you?
Behind the times 12 Mar 2003
Format:Paperback
This book is showing its age The author's fixation with 'code and fix' and it's attendant evils, notably starting coding early on in a project, whilst justified ignores the existence of Agile Methods, Test Driven Development and Refactoring which allow for a code-centric way of working that delivers early visible progress whilst keeping the software 'soft' and scalable.

I would recommend Martin Fowler's excellent 'Refactoring' instead. Having said that, McConnell's 'Code Complete' is brilliant.

Comment | 
Was this review helpful to you?

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 

Search Customer Discussions
Search all Amazon discussions
   


Listmania!

Create a Listmania! list

Look for similar items by category


Look for similar items by subject


Feedback