- Pasta blanda: 431 páginas
- Editor: Prentice Hall; Edición: 1 (1 de agosto de 2008)
- Idioma: Inglés
- ISBN-10: 9780132350884
- ISBN-13: 978-0132350884
- ASIN: 0132350882
- Dimensiones del producto: 17.8 x 3 x 23.4 cm
- Peso del envío: 816 g
- Opinión media de los clientes sobre el producto: 6 opiniones de clientes
- Clasificación en los más vendidos de Amazon: nº9,518 en Libros (Ver el Top 100 en Libros)
Retroceder
Avanzar
Clean Code: A Handbook of Agile Software Craftsmanship (Inglés) Pasta blanda – ago 2008
Ver todos los 2 formatos y ediciones
Ocultar otros formatos y ediciones
|
Precio de Amazon
|
Nuevo desde | Usado desde |
Los clientes que compraron este producto también compraron
Página 1 de 1 Volver al inicioPágina 1 de 1
Comienza a leer Clean Code en tu Kindle en menos de un minuto.
¿No tienes un Kindle? Compra tu Kindle aquí o descarga una aplicación de lectura Kindle GRATUITA.
¿No tienes un Kindle? Compra tu Kindle aquí o descarga una aplicación de lectura Kindle GRATUITA.
 |
Detalles del producto |
Descripción del producto
Descripción del producto
Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer-but only if you work at it. What kind of work will you be doing? You'll be reading code-lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code-of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Contraportada
Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way.
Noted software expert Robert C. Martin presents a revolutionary paradigm with "Clean Code: A Handbook of Agile Software Craftsmanship." Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer--but only if you work at it.
What kind of work will you be doing? You'll be reading code--lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.
"Clean Code" is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code--of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.
Readers will come away from this book understanding
How to tell the difference between good and bad codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readabilityHow to implement complete error handling without obscuring code logicHow to unit test and practice test-driven developmentThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Noted software expert Robert C. Martin presents a revolutionary paradigm with "Clean Code: A Handbook of Agile Software Craftsmanship." Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer--but only if you work at it.
What kind of work will you be doing? You'll be reading code--lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.
"Clean Code" is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code--of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.
Readers will come away from this book understanding
How to tell the difference between good and bad codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readabilityHow to implement complete error handling without obscuring code logicHow to unit test and practice test-driven developmentThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Más información del producto
|
|
|
|
|
|
|---|---|---|---|---|---|
| A Handbook of Agile Software Craftsmanship | Practical Advice for the Professional Programmer | A Craftsman's Guide to Software Structure and Design | Professionalism, Pragmatism, Pride | Get Better Performance Out of Your Legacy Systems | |
| Title | Clean Code | Clean Coder | Clean Architecture | The Software Craftsman | Working Effectively with Legacy Code |
| Core Concept | Best agile practices of cleaning code “on the fly” that will instill within you the values of a software craftsman and make you a better programmer—but only if you work at it. | Robert C. Martin introduces the disciplines, techniques, tools, and practices of true software craftsmanship. This book is packed with practical advice–about everything from estimating and coding to refactoring and testing. | Uncle Bob presents the universal rules of software architecture that will help you dramatically improve developer productivity throughout the life of any software system. | Sandro Mancuso helped found the world’s largest organization of software craftsmen; now, he shares what he’s learned through inspiring examples and pragmatic advice you can use in your company, your projects, and your career. | Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts. Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. |
| Endoresement | "It is the best pragmatic application of Lean principles to software I have ever seen in print." —James O. Coplien, Founder of the Pasteur Organizational Patterns project | “Some technical books inspire and teach; some delight and amuse. Rarely does a technical book do all four of these things. Read, learn, and live the lessons in this book and you can accurately call yourself a software professional.” —George Bullock Senior Program Manager Microsoft Corp. | "A good architecture comes from understanding it more as a journey than as a destination, more as an ongoing process of enquiry than as a frozen artifact." -- Kevlin Henney | "If you are the type of programmer, team lead, or manager who craves to be able to go home after a long day of work, look in the mirror, and say, 'Damn, I did a good job today!' then this is the book for you." -- Robert C. Martin | "This book describes a set of disciplines, concepts, and attitudes that you will carry with you for the rest of your career and that will help you to turn systems that gradually degrade into systems that gradually improve." --- Robert C. Martin |
Los clientes que vieron este producto también vieron
Página 1 de 1 Volver al inicioPágina 1 de 1
6 opiniones de clientes
| 5 estrellas |
| 4 estrellas |
| 3 estrellas (0%) |
| 2 estrellas (0%) |
| 1 estrella (0%) |
Escribir reseña sobre este producto
Mostrando 1-6 de 6 opiniones
Ha surgido un problema al filtrar las opiniones justo en este momento. Vuelva a intentarlo en otro momento.
19 de julio de 2017
Formato: Pasta blandaCompra verificada
Comentar
Informar de un abuso
22 de noviembre de 2016
Formato: Pasta blandaCompra verificada
26 de febrero de 2018
Formato: Edición KindleCompra verificada
| |||||