Clean Code: A Handbook of Agile Software Craftsmanship.

By:

Martin, Robert C

Language: English Publication details: United States Pearson Addison-Wesley 2008Description: xxix, 431 pages; Figures, tablesISBN:

9780132350884

Subject(s):

DDC classification:

005.1 M379

Contents:

-Chapter 1: Clean Code -Chapter 2: Meaningful Names -Chapter 3: Functions -Chapter 4: Comments -Chapter 5: Formatting -Chapter 6: Objects and Data Structures -Chapter 7: Error Handling -Chapter 8: Boundaries -Chapter 9: Unit Tests -Chapter 10: Classes -Chapter 11: Systems -Chapter 12: Emergence -Chapter 13: Concurrency -Chapter 14: Successive Refinement -Chapter 15: JUnit Internals -Chapter 16: Refactoring SerialDate -Chapter 17: Smells and Heuristics

Summary: Even bad code can function. But if code isn’t clean, it can bring a development organisation 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 distil their best agile practice of cleaning code “on the fly” into a book that will instil 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.

Tags from this library: No tags from this library for this title. Log in to add tags.

Average rating: 0.0 (0 votes)

Holdings
Item type	Current library	Call number	Copy number	Status	Date due	Barcode
Libros	CIBESPAM-MFL	005.1 / M379 (Browse shelf(Opens below))	Ej: 1	Available		006071

-Chapter 1: Clean Code
-Chapter 2: Meaningful Names
-Chapter 3: Functions
-Chapter 4: Comments
-Chapter 5: Formatting
-Chapter 6: Objects and Data Structures
-Chapter 7: Error Handling
-Chapter 8: Boundaries
-Chapter 9: Unit Tests
-Chapter 10: Classes
-Chapter 11: Systems
-Chapter 12: Emergence
-Chapter 13: Concurrency
-Chapter 14: Successive Refinement
-Chapter 15: JUnit Internals
-Chapter 16: Refactoring SerialDate
-Chapter 17: Smells and Heuristics

Even bad code can function. But if code isn’t clean, it can bring a development organisation 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 distil their best agile practice of cleaning code “on the fly” into a book that will instil 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.

There are no comments on this title.

to post a comment.