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

Overview

In this newest addition to Microsoft Press' acclaimed Best Practices series, award-winning author Steve McConnell offers candid reflections and a look ahead at the software engineering profession from one of the industry's most highly regarded practitioners. After the Gold Rush: Creating a True Profession of Software Engineering 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. ...
See more details below
Available through our Marketplace sellers.
Other sellers (Paperback)
  • All (28) from $1.99   
  • New (3) from $1.99   
  • Used (25) from $1.99   
Close
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$1.99
Seller since 2008

Feedback rating:

(94)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New
1999 Paperback New Ships Fast! Satisfaction Guaranteed!

Ships from: Skokie, IL

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
$9.48
Seller since 2008

Feedback rating:

(169)

Condition: New
0735608776 BRAND NEW NEVER USED IN STOCK 125,000+ HAPPY CUSTOMERS SHIP EVERY DAY WITH FREE TRACKING NUMBER

Ships from: fallbrook, CA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$50.00
Seller since 2014

Feedback rating:

(178)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Close
Sort by
Sending request ...

Overview

In this newest addition to Microsoft Press' acclaimed Best Practices series, award-winning author Steve McConnell offers candid reflections and a look ahead at the software engineering profession from one of the industry's most highly regarded practitioners. After the Gold Rush: Creating a True Profession of Software Engineering 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 sometimes 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.
  • Lively and highly readable introspections on the software development industry that will appeal to both insiders and nontechnical readers alike
  • Candid reflections and a look at the future of software engineering as a profession from one of the industry's most highly regarded practitioners
  • Describes software development practices and trends in a readable and thought-provoking series of essays
  • Provides valuable insights that can help software developers plan their careers
  • Gives the nontechnical public an understanding of software engineering as it is today and as it could be
  • The esteemed editor of IEEE Software, author Steve McConnell has written three previous bestselling and award-winning Best Practices books
Read More Show Less

Product Details

  • ISBN-13: 9780735608771
  • Publisher: Microsoft Press
  • Publication date: 11/1/1999
  • Series: DV-Best Practices Series
  • Edition number: 1
  • Pages: 182
  • Product dimensions: 7.39 (w) x 9.17 (h) x 0.66 (d)

Meet the Author


Steve McConnell is Chief Software Engineer at Construx Software Builders, Bellevue, Washington, where he divides his time among leading custom software projects, consulting on other companies' software projects, and writing books and articles. He is the author of Code Complete, Rapid Development, and Software Project Survival Guide. Steve has also written numerous technical articles and edits IEEE Software.
Read More Show Less

Read an Excerpt


Chapter 1: Software Dinosaurs


"He that will not apply new remedies must expect new
evils for time is the greatest innovator."
-Francis Bacon

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.' Brooks predicted that the software engineering tar pit would continue to be sticky for a long time to come. The problems that Brooks described twenty-five years ago were not new when he described them, and the software community has now had another quarter century to work on them. How much has the situation changed?

Schedule pressure is a common feature of today's projects. According to some estimates, excessive schedule pressure occurs in about 75 percent of all medium-size projects and in 90 percent or more of all large projects. Overtime is more the norm than the exception. Internet startups are known for the long hours they expect from their employees, and stories of programmers sleeping under their desks abound. But this isn't a new phenomenon. As far back as the mid-1960s, one report stated that, "In many companies, programmers faced with deadlines have been known to spend nights in their offices." In 1975, Fred Brooks pointed out that "more software projects have gone awry for lack of calendar time than all other causes combined." Schedule overruns have been around for at least 30 years (probably since time immemorial).

Many people today complain about the shortage of qualified software developers. Experts estimate that North America is now experiencing a software personnel shortage of about 10 percent. This is not a new problem either. Thirty years ago, total employment was estimated at 100,000 programming jobs in the United States, and experts estimated that 50,000 additional jobs were available-a 33 percent labor shortage that makes today's 10 percent labor shortage seem almost insignificant.

The scope of today's large software projects seems daunting, and a natural tendency is to think that no one ever attempted projects of the scope we now face. Yet even a huge project such as the initial development of Microsoft Windows NT has historical precedents. The initial Windows NT project required about 1,500 staff-years of effort, but the development of IBM's OS/360, which was completed in 1966, required more than three times as much effort.

Recent surveys have found that the most frequent causes of software project failure have to do with requirements problems-requirements that are too vague to be implemented, that contradict each other, or that change frequently and wreak havoc on the system design. But requirements problems are not new. Back in 1969, Robert Frosch observed that a system could "satisfy the letter of the specification and still not be very satisfactory."

Modem developers rack their brains trying to keep up with the frenetic pace of change brought on by Internet development. How do you keep up with new languages, shifting standards, and vendors that release new products every few months? To those of us who were in the software world 15 years ago, this predicament sounds an awful lot like the mid-1980s when the IBM PC began to revolutionize corporate computing.

When the Fortran programming language was developed in 1954-58, it was supposed to eliminate the need for computer programming--scientists and engineers could simply enter their formulas into the computer, and the computer would translate the formulas for them, thus the name FORmula TRANslation. Of course, Fortran didn't eliminate programming; it just reduced the need for machine-language programming. From time to time we still hear about the promise of automatic programming-computers will become so advanced that the need for computer programmers will disappear. But this conjecture was already a well-polished chestnut 30 years ago when Gene Bylinsky reported that, "Predictions of businessmen blithely conversing with their omnipotent machines in plain English still get played up regularly in the press." The reality is that defining problems in painstaking detail is difficult work that can't be automated. That aspect of computer programming will not go away. New tools are useful, but not a substitute for clear thinking. I made that point in my 1996 book Rapid Development; Robert Frosch had already made the same point in IEEE Spectrum 30 years earlier.

Internet developers talk about development in Internet time. The Internet makes it possible for developers to roll out revisions to their programs with unprecedented ease. CDs and DVDs don't have to be duplicated; users can download upgrades electronically, making delivery of upgrades quick and inexpensive. This ease of distribution contributes to pressure to release upgrades frequently in response to user requests. Internet developers say that users would rather get the software quickly than have it be perfect. Users will tolerate low reliability. According to Internet developers, "It's better to be first than right."

How unprecedented are these dynamics really? Some Internet developers think they are unique to web projects, but industry old-timers know better: low rollout cost, easy corrections, and low cost of failure sound like a good old-fashioned in-house mainframe production environment.

The common threads tying together over 25 years of software development-schedule pressure, staff shortages, large projects, faulty requirements volatile technology, and even development in Internet time-are a source of both comfort and despair. The despair arises from the fact that some problems have been with us for a quarter century or more and are still common. We truly have been stuck in the tar pit a long time. But we've been staring at the same problems long enough to recognize some patterns, and some software organizations have escaped the tar pit's sticky grip. Therein lies the comfort.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Anonymous

    Posted November 11, 2000

    This book is Right On!!

    This book has hit the mark right on for what we need to do with the software industry. I've added it as encouraged reading for every developer at our company. Any developer who reads this book will have his/her eyes opened as to what it takes to be a real Software Engineer, rather than just a code and fix programmer. I really felt good after reading this book; it made me feel really positive about the Software engineering industry and where we are headed. Right On Steve!! I'm glad someone has it all figured out!!

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)