Rating: 
Summary: A useful book, but take with a pinch of salt
Review: Firstly, this is a pretty good read as computer books go. It contains a lot of good information in an easily digestible fashion.It's a good book to learn about a range of contemporary (ish) issues in IT - software processes, CASE tools, QA, metrics reuse etc etc. Short chapters and Yourdon's chatty style help greatly. The chapter on recommended reading has some great pointers too. The negatives are that it's pretty superficial at times and reads very much like a consultant / salesman selling his wares rather than someone who actually runs projects for a living. In particular, the chapter on software methodologies seemed very simplistic to me (and I have had experience of many, believe me!) Still, all in all I'd recommend this to any IT profesional who feels he/she is only exposed to a narrow range of software tools & methods and wants to know more about what else is out there.
Rating: 
Summary: A 'must read ', but for historical reasons only
Review: Five years after reading this book when it was first published, I bought a secondhand copy (as well as a copy of Rise and Resurrection) to take another look. Obviously, the American Programmer is in decline, so Ed Yourdan got that right. The question is whether the book has anything important to say to us today. This is a book about case tools. Anybody remember them? Yourdan's argument was that the willingness of Indian programmers to use case tools would enable them to produce good, cheap software at a fraction of the cost of that generated by American 'cowboys'. His strong advice for programmers in the US was to start using mechanistic methods, so that they could also start churning out code like cookies in a cookie factory. Most probably, Decline and Fall will remain an interesting book for students of computer science to read for many years into the future - not for what it got right, but for what it got wrong. Common wisdom today (which may become foolishness tomorrow) is that American Programmers can't hope to compete against people living in poor nations by trying to undercut them on cost, but only by using their native creativity and willingness to explore new frontiers to create truly new products. In other words, Yourdan correctly forsaw the future, but badly misjudged the solution.
Rating: 
Summary: People STILL Buy This Thing???
Review: HAHAHAHA!!! Ed Yourdon's classic 'the American software industry is going to hell in a handcart any second now, cuz Ed sez so' tome. After the better part of a decade since its original publication, with American software still going strong, the hyperbole about USA programmers sliding off onto the continental shelf can only be taken as comedy. Are there quality issues with the way most commercial software is produced? Undoubtedly. It is to a level where we need self appointed Cassandras screaming of imminent doom? Sorry, but the marketplace determines that. And when it comes to the majority of software, people and companies do buy it. You want perfect, bug free code? Then get customers (more importantly, software producing companies/management) to wait until it is COMPLETELY DONE. Unfortunately, like most gloom and doomer's, Yourdon has a ready made 'fix' to avert looming catastrophe; surprise! He thinks everyone should follow the Ed methods of doing things. This couldn't make him a boatload of money, could it? Hmmm... And to top it all off, most of Ed's methods involve 'preventing' the 'evil coders' from fouling the 'beneficent, wondrous' designs of the system architects with their own silly ideas. Sorry, but when you can genuinely perform empirical measurements based on the 'blueprints' of as yet unbuilt software systems, then that idea may finally make some sense. Unfortunately, the software engineering equivalent of the Roman arch has yet to be discovered. So, if any coders out there are really enamored of all of Ed's 'remedies', then I hope you enjoy being chained to an oar in his philosophical coding slave galley. Yourdon does have some good ideas in amongst the rest, but nothing I haven't heard elsewhere.
Rating: 
Summary: Tremendous insight into the software industry
Review: I first read this book about five years ago, and loved it. Anyone in the software industry who sees being a software engineer as just "coding" should read this book. It provides insight into all areas of "software technology" and why they are important to software engineers. Of particular interest was the Peopleware chapter, which talks about how software engineers should be managed and treated, and the Programmer's Bookshelf appendix, which provided lots of great additional reading material. Overall, a really easy to read, one of a kind book.
Rating:
Summary: Tremendous insight into the software industry
Review: I first read this book about five years ago, and loved it. Anyone in the software industry who sees being a software engineer as just "coding" should read this book. It provides insight into all areas of "software technology" and why they are important to software engineers. Of particular interest was the Peopleware chapter, which talks about how software engineers should be managed and treated, and the Programmer's Bookshelf appendix, which provided lots of great additional reading material. Overall, a really easy to read, one of a kind book.
Rating:
Summary: Plausible possibility. Feeble solutions.
Review: I never bought the book but read it in one sitting at a bookstore a few years ago. I had every intention of buying the book but when I casually started viewing it, I could not put it down. By the time I was ready to make a purchase, I already read the book. (Sorry, Ed). The author is no stranger to controversy and I must admit the book at the time provoked everything from fear and anger to denial in me regarding my chosen profession. Although it's publication predates the emergence of the Internet and the vast changes that have taken place since then, industry guru Ed Yourdon gives a rather plausible thesis as to why software development could move overseas. There is no question that software engineering in India has developed a worlwide reputation for high quality and only now, in the last 3 years has the realization of his prophecy accelerated. However, the main impetus behind this trend has been to take advantage of the cheaper labor pool. It is for this reason I find the author's proposed solutions to be feeble. Increased use of CASE tools, object-oriented methods, and iterative development may improve the quality of American software but doesn't remotely address the enormous salary differential between say, Indian programmers and their American counterparts. Quality and innovation can only go so far and these practices are now already standard and widespread throught the industry. That said, even the book's thesis is not without it's problems. The author does not seem to take into account that the workforce in the American software industry is much more diverse than it was 10 or 15 years ago, making the situation more complicated than the stereotypical lazy white guys competing against the rest of the world. Nearly a quarter of my colleagues are from India and there's no reason to suspect they're any less smarter than professionals in Bangalore. Also, the focus of the book seems to be on writing code. If that was all there was to developing and supporting information systems, I'd be inclined to agree with the author 100%. As it happens, the most complicated aspects of system development isn't always writing the code or even design, but communication involving everything from requirements analysis to coordination of development for various parts of the system encompassing database changes as well as client and middleware components. This is not to say it would be impossible to coordinate that with people on the other side of the world but difficult. It IS possible and has been tried but the results have been mixed. If my employer were to try this, they may very well save on programmer costs only to see their savings eaten up by new costs in communication infrastructure, endless business trips, more meetings... The bottom line: Software development will continue to be delegated to oversees firms and will have a profound effect on some job prospects here and on the nature of the work itself, but the American programmer is far from becoming an endangered species.
Rating:
Summary: Plausible possibility. Feeble solutions.
Review: I never bought the book but read it in one sitting at a bookstore a few years ago. I had every intention of buying the book but when I casually started viewing it, I could not put it down. By the time I was ready to make a purchase, I already read the book. (Sorry, Ed). The author is no stranger to controversy and I must admit the book at the time provoked everything from fear and anger to denial in me regarding my chosen profession. Although it's publication predates the emergence of the Internet and the vast changes that have taken place since then, industry guru Ed Yourdon gives a rather plausible thesis as to why software development could move overseas. There is no question that software engineering in India has developed a worlwide reputation for high quality and only now, in the last 3 years has the realization of his prophecy accelerated. However, the main impetus behind this trend has been to take advantage of the cheaper labor pool. It is for this reason I find the author's proposed solutions to be feeble. Increased use of CASE tools, object-oriented methods, and iterative development may improve the quality of American software but doesn't remotely address the enormous salary differential between say, Indian programmers and their American counterparts. Quality and innovation can only go so far and these practices are now already standard and widespread throught the industry. That said, even the book's thesis is not without it's problems. The author does not seem to take into account that the workforce in the American software industry is much more diverse than it was 10 or 15 years ago, making the situation more complicated than the stereotypical lazy white guys competing against the rest of the world. Nearly a quarter of my colleagues are from India and there's no reason to suspect they're any less smarter than professionals in Bangalore. Also, the focus of the book seems to be on writing code. If that was all there was to developing and supporting information systems, I'd be inclined to agree with the author 100%. As it happens, the most complicated aspects of system development isn't always writing the code or even design, but communication involving everything from requirements analysis to coordination of development for various parts of the system encompassing database changes as well as client and middleware components. This is not to say it would be impossible to coordinate that with people on the other side of the world but difficult. It IS possible and has been tried but the results have been mixed. If my employer were to try this, they may very well save on programmer costs only to see their savings eaten up by new costs in communication infrastructure, endless business trips, more meetings... The bottom line: Software development will continue to be delegated to oversees firms and will have a profound effect on some job prospects here and on the nature of the work itself, but the American programmer is far from becoming an endangered species.
Rating:
Summary: A wonderful book full of insight
Review: I read this book as a grad student is I.S. Management. Provides wonderful insight into how to and how not to manage IS. Chapter 8 is a must for any and all developers. Great insight into what wrong with U.S. IT professionals. Recommended for all IT professionals
Rating:
Summary: Free Upgrade?
Review: If the author followed his own guidelines for quality management, he would offer every owner of this book a free upgrade to "Resurrection of the American Programmer", in which he explains why he was so wrong in this book. But I think you'd be better off refusing the upgrade, and going with DeMarco, Beck, or Fowler.
Rating:
Summary: Free Upgrade?
Review: If the author followed his own guidelines for quality management, he would offer every owner of this book a free upgrade to "Resurrection of the American Programmer", in which he explains why he was so wrong in this book. But I think you'd be better off refusing the upgrade, and going with DeMarco, Beck, or Fowler.
| 
