000			02747ntdaa2200277 ab4500
003			UnInEc
005			20240104114529.0
006			a||||g ||i| 00| 0
008			140501s9999 mx ||||f |||| 00| 0 spa d
020			_a9780132350884
040			_aCIBESPAM MFL
041			_aeng
082			_a005.1 _bM379
100			_aMartin, Robert C.
245			_aClean Code: A Handbook of Agile Software Craftsmanship.
260			_aUnited States _bPearson _bAddison-Wesley _c2008
300			_axxix, 431 pages; _bFigures, tables;
505			_a-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
520			_aEven 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.
650			_aComputer Sofware
650			_aAgile software development
650			_aReliability
912			_c2024-01-04 _dPaúl Villacreses
913			_aTIC _bCC _dSCSAS
942			_2ddc _cBK
999			_c13030 _d13030