EUR 39,60
  • Precio recomendado: EUR 41,60
  • Ahorras: EUR 2,00 (5%)
  • Precio final del producto
Envío GRATIS. Ver detalles.
En stock.
Vendido y enviado por Amazon. Se puede envolver para regalo.
Code Complete: A Practica... se ha añadido a la cesta
¿Tienes uno para vender?
Volver atrás Ir adelante
Escuchar Reproduciendo... Interrumpido   Estás escuchando una muestra de la edición de audio Audible.
Más información
Ver las 3 imágenes

Code Complete: A Practical Handbook of Software Costruction (Dv Professional) (Inglés) Tapa blanda – 19 jun 2004

4.8 de un máximo de 5 estrellas 4 opiniones de clientes

Ver los formatos y ediciones Ocultar otros formatos y ediciones
Precio Amazon
Nuevo desde Usado desde
Versión Kindle
"Vuelva a intentarlo"
Tapa blanda
"Vuelva a intentarlo"
EUR 39,60
EUR 30,54 EUR 34,52
click to open popover

Comprados juntos habitualmente

  • Code Complete: A Practical Handbook of Software Costruction (Dv Professional)
  • +
  • Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin)
  • +
  • Pragmatic programmer: from journeyman to master
Precio total: EUR 120,55
Comprar los productos seleccionados conjuntamente

Descripción del producto

Reseña del editor

Widely considered one of the best practical guides to programming, Steve McConnell’s original CODE COMPLETE has been helping developers write better software for more than a decade. Now this classic book has been fully updated and revised with leading-edge practices—and hundreds of new code samples—illustrating the art and science of software construction. Capturing the body of knowledge available from research, academia, and everyday commercial practice, McConnell synthesizes the most effective techniques and must-know principles into clear, pragmatic guidance. No matter what your experience level, development environment, or project size, this book will inform and stimulate your thinking—and help you build the highest quality code.

Discover the timeless techniques and strategies that help you:

  • Design for minimum complexity and maximum creativity
  • Reap the benefits of collaborative development
  • Apply defensive programming techniques to reduce and flush out errors
  • Exploit opportunities to refactor—or evolve—code, and do it safely
  • Use construction practices that are right-weight for your project
  • Debug problems quickly and effectively
  • Resolve critical construction issues early and correctly
  • Build quality into the beginning, middle, and end of your project

Biografía del autor

Steve McConnell is recognized as one of the premier authors and voices in the development community. He is Chief Software Engineer of Construx Software and was the lead developer of Construx Estimate and of SPC Estimate Professional, winner of Software Development magazine's Productivity Award. He is the author of several books, including Code Complete and Rapid Development, both honored with Software Development magazine's Jolt Award.

No es necesario ningún dispositivo Kindle. Descárgate una de las apps de Kindle gratuitas para comenzar a leer libros Kindle en tu smartphone, tablet u ordenador.

  • Apple
  • Android
  • Windows Phone

Obtén la app gratuita:

Detalles del producto

Opiniones de clientes

4.8 de un máximo de 5 estrellas
5 estrellas
4 estrellas
3 estrellas
2 estrellas
1 estrella
Ver las 4 opiniones de clientes
Comparte tu opinión con otros clientes

Principales opiniones de clientes

Formato: Tapa blanda Compra verificada
Una obra imprescindible para programadores y analistas que quieran acercarse al mundo de la programación informática de forma completa y didáctica con el estilo inmejorable de Steve McConnell.
Comentario A una persona le ha parecido esto útil. ¿Esta opinión te ha parecido útil? No Enviando comentario...
Gracias por tu opinión.
Lo sentimos, no hemos podido registrar tu voto. Vuelva a intentarlo
Informar de un abuso
Formato: Tapa blanda Compra verificada
No podría describir con palabras lo que esta obra me ha aportado para mi trabajo diario. Resume en casi 900 páginas la experiencia en el desarrollo de software de toda una carrera profesional. Cualquier persona que quiera mejorar como desarrollador de software debería tenerlo en su estantería.
Comentario ¿Esta opinión te ha parecido útil? No Enviando comentario...
Gracias por tu opinión.
Lo sentimos, no hemos podido registrar tu voto. Vuelva a intentarlo
Informar de un abuso
Formato: Tapa blanda Compra verificada
What I liked the most about this book is not its comprehensive exposition of every aspect of every task a programmer must face, but that every advice is reasoned and based, as far as possible, in facts and studies.
Comentario ¿Esta opinión te ha parecido útil? No Enviando comentario...
Gracias por tu opinión.
Lo sentimos, no hemos podido registrar tu voto. Vuelva a intentarlo
Informar de un abuso
Formato: Tapa blanda Compra verificada
El libro es un poco "biblia" pero es que es eso, la "biblia" de la programación. Si tenéis que compraros un libro, primero el Clean Code y después éste.
Comentario ¿Esta opinión te ha parecido útil? No Enviando comentario...
Gracias por tu opinión.
Lo sentimos, no hemos podido registrar tu voto. Vuelva a intentarlo
Informar de un abuso

Opiniones de clientes más útiles en (beta) 4.6 de un máximo de 5 estrellas 289 opiniones
225 de 228 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas A wonderfully practical guide to programming 3 de mayo de 2011
Por Alexandros Gezerlis - Publicado en
Formato: Tapa blanda Compra verificada
The tragedy for books that become classics is that there are many more people who have heard of them (or perhaps also bought them) than people who have read them. In this case, the fact that Steve McConnell's "Code Complete" is approximately 900 pages long doesn't help, either. Even so, this is a book that not only deserves to be read, but also rewards multiple readings.

The Good: McConnell deserves credit for writing the first (and only?) readable encyclopedia of best practices on software quality, covering topics such as how to build classes, use data and control structures, debug, refactor, and code-tune. Yes, it would be nice if the book was updated to include substantive material on languages like Ruby or Python (cf. p. 65, Python "also contains some support for creating larger programs") but, in the words of Gertrude Stein, "Not everything can be about everything" -- though Code Complete does come pretty close. This book contains an astonishing number of practical points on a variety of topics. Here is a quasi-random selection: a) don't use booleans as status variables (chs. 5, 12), b) when you feel the need to override a function and have it do nothing, don't; refactor instead (ch. 6), c) when choosing variable names, avoid homonyms (ch. 11), d) if you decide to use a goto, indenting your code properly will be difficult or impossible (ch. 17), e) trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often (ch. 22), f) make your code so good that you don't need comments, and then comment it to make it even better (ch. 32), and finally the oft-repeated g) you should try to program into your language, not in it (ch. 34). McConnell also sprinkles the text with classic words of wisdom, e.g. "The competent programmer is fully aware of the strictly limited size of his own skull" (Edsger Dijkstra), "Never debug standing up" (Gerald Weinberg), "Copy and paste is a design error" (David Parnas), "Any fool can defend his or her mistakes -- and most fools do." (Dale Carnegie). It is important to point out that even though this volume is encyclopedia-like, it does have both a sense of humor (e.g. "the encryption algorithm is so convoluted that it seems like it's been used on itself") and a clear authorial voice (e.g. "Though sometimes tempting, that's dumb."). Another example of the latter: in ch. 33, after quoting Edward Yourdon at length, McConnell adds "This lusty tribute to programming machismo is pure B.S. and an almost certain recipe for failure".

The Bad: overall the writing is very good, but the occasional infelicity reminds us that McConnell is human (e.g. p. 369 "A loop-with-exit loop is a loop in which", p. 809 "A program contains all the routines in a program."). In a technical book of this breadth, minor mistakes are bound to creep in. For example, in ch. 10 McConnell mentions the different possible levels of a variable's scope in C++, and then adds that in Java and C# one can also use namespaces, thus effectively ignoring the existence of the namespace concept in C++ (which is baffling, given that he then discusses precisely that topic in ch. 11). Another example, this one more serious, is McConnell's recommendation that you should use a pointer - not a reference - if you want to pass by reference in C++ (ch. 13), something which is contrary to C++ best practices (see e.g. Sutter & Alexandrescu, "C++ Coding Standards", Item 25). A less technical point: in ch.2 McConnell criticizes Frederick Brooks for writing (in 1975): "Plan to throw one away; you will, anyhow". I found this to be bizarre, given that in the 1995 edition of "The Mythical Man-Month" Brooks states in no uncertain terms that he has changed his mind on this: "This I now perceive to be wrong" (p. 265). Given that Code Complete 2 was published nearly 10 years later (in 2004), criticizing Brooks for his publicly repudiated former opinion seems improper. On a different note, although some of the on-line accompanying material is fascinating (e.g. the links to the original Dijkstra and Lawrence articles in ch. 17) many of the links are just electronic versions of McConnell's checklists or bibliographies, while some are simply disappointing. To name only a couple of these, as of this writing the link on p. 856 on the economics of XP is a dead link, while the one on p. 76 is downright embarrassing (it links to a google search for "emergent design"). Finally, even though the book has a dedicated website, no list of errata is provided there. If you dig deeper, you can find one on the O'Reilly website, but that is woefully inadequate, e.g. it contains no information on separate printings.

The most common criticism one hears about this book is that any decent software developer should already know the material covered in it. Ironically enough, this is true. To quote Dr. Johnson: "People need to be reminded more often than they need to be instructed".

Alex Gezerlis
282 de 302 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas A Great S/W Dev't Guide Got Even Better 23 de julio de 2004
Por Steve Bailey - Publicado en
Formato: Tapa blanda
It was a pleasure to find out that this book had been updated when I reads news of it. CC2 is a great one-stop 'place' to go to when you want a great excuse to apply Stephen Covey's 'Sharpen The Saw' principle. This updated version has some solid, fantastic, expert instruction on designing from scratch, whether it's OO, writing better routines, psuedocode, nested loops, or at the higher level: agile methods, etc..
McConnell's approach of talking to you, the programmer, is ideal: not too much humor, and an easy to read, but professional approach in the way he donates the contents of his brain: i.e. McConnell's lengthy experience in the field.

I read just a couple of paragraphs in a chapter before work one morning, and the advice I picked up saved so much time that same day. And it wasn't even specific to coding instruction. It was a piece of advice on a philosophy on how he personally determines how much upfront design he should settle on before coding.

Reading Software Construction material of this caliber, as compared to some, yet another, new book on a specific language that might look impressive to know, is what makes for a solid programmer.

Refreshing your overall S/W construction knowledge gives you so much more of your life back, because you will have way less bugs and a lot more fun maintaining the high-quality code you are now writing because of CC2.
I mentioned already that he covers OO, but I wanted to emphasize the excellent material he offers in this area. I am now seeing the benefit of measuring the quality of your classes by this guideline: are they true Abstract Data Types. ( rather than just trying to use the syntax that the language provides to its potential).
Great job on a rather thorough re-write of a S/W development staple.
140 de 150 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas The definitive book on software construction. 4 de agosto de 2006
Por Steven - Publicado en
Formato: Tapa blanda Compra verificada
I don't know how much more I can say about this book that hasn't been said already but I will do my best to describe my experience with this book.

Have you ever looked at a class, or a method that seems to work fine but it just doesn't "feel" right? For some reason it seems as if that method or class may be hard to debug in the future or that the code is hard to understand. Or have you gone back to a class file you wrote months ago and you spend an awful lot of time trying to figure out what the heck is going on with that class file? Maybe the methods in the class are spaghetti like in nature, or maybe the names of your methods don't have a very good description so it's hard to figure out how everything ties together. I have had this problem. This book will teach you how to get out of those habits. You will learn what a solid class or method looks like. You will learn how properly naming your classes and methods can greatly reduce complexity in the long run. Everything is backed by hard evidence. I should also mention that this is just one chapter in this wonderful book.

This book really drills down proper programming practices. A lot of times you may read a passage and think to yourself "well, of course!"... but then you realize you don't practice what's contained in the passage you just read. This book is great for both new programmers and experienced programmers alike. New programmers benefit greatly because they will learn how to construct software properly without having to go through all of the hoops. Experienced programmers will also learn a great deal, as well as be reminded that some of their habits that they've developed over the years can hinder production and cause software development to become more complex then it really is.

Steve writes in a very clean style. It's very easy to read. You don't need to memorize anything in a book like this, instead you just need to gain an understanding of the concepts he brings forth. After reading this book I definitely follow a lot of his advice. When I build a new class, method or what-have-you I get a certain feeling of when it seems right and when something seems wrong. I am now much better at analyzing my code and figuring out what doesn't seem correct and I take his advice I learned in this book to help me to figure out - and correct the problem. After reading this book I feel like a lot of my rough edges as a developer have been rounded out. I feel as if I gained a years worth of experience just by reading this book.

This book is friendly for any software developer. The concepts he presents apply to all languages. This is a book that teaches you how to think about programming better and how to construct good solid code. This is one of the best books I've ever read. If you're even thinking about buying this book, then buy it.
23 de 24 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas as good as everyone says it is 21 de octubre de 2006
Por Thing with a hook - Publicado en
Formato: Tapa blanda
Code Complete pops up regularly on the lists of the 'read this book or you'll never get a job and everyone else will laugh at you' genre, so if you're easily influenced, like me, you may approach this book with an air of duty rather than anticipation. Fortunately, despite its heft, this is well worth the plaudits that have been heaped upon it. I actually enjoyed this more than The Pragmatic Programmer and Programming Pearls, two books often mentioned in the same breath as this tome.

CC covers pretty much every part of the software development lifecycle, from planning to code reviews to testing. These are all pretty good discussions, but the best bit is definitely the chapters on coding. Most of the examples are in Visual Basic or Java, so you'd do well to know one of those languages.

When it comes to object modelling, there's actually a reasonable set of guidelines harvestable from literature, and languages tend to diverge more on issues of packaging, so CC is at its best at the lower level procedural details of code layout, formatting, loop construction, optimisation and so on. Many books claim to provide coding guidelines, but don't do much beyond stating the obvious like (for Java) "use camel case for variable names", "start class names with capital letters" and "avoid Hungarian notation". CC is different because it actually provides useful recommendations. As an example, there's a very good discussion on when and where the use of loop-breaking constructs like break and continue ('next' in Ruby and Perl) are appropriate. Few (if any) other books provide this sort of practical detail.

It's well-written, with just the right amount of humour in its exhortations - the withering references to coders who investigate loop bugs by randomly adjusting the termination criterion up or down by one until it works raised a wry smile from this reviewer.

To summarise, this is a collection of best practices distilled from a pretty huge amount of reading, and is genuinely helpful. I would certainly point any programming beginner at this book.
30 de 34 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas CC2 is a 'Must Have' 23 de julio de 2004
Por Daryl Sant - Publicado en
Formato: Tapa blanda
Code Complete, first edition, has long been regarded as ?The Bible? for software development. Dare I say, CC2 is even better than the original. It has been thoroughly updated to include OO, internet and web development, as well as new best practices such as test-first development, pair programming, and refactoring.

Steve McConnell provides a balanced, thoughtful discussion of competing approaches to software development. He also provides a wealth of references to additional materials covering specific topics in more detail. In a field that is often defined by religious arguments, CC2 stays objective on most topics. At the same time, McConnell does not shy away from stating his conclusions on topics that he believes have a clear-cut ?best choice?.

Overall, this book is as much of a ?must have? as the first edition and destined to become just as famous.