000			04191cam a2200457 i 4500
001			15315370
005			20230529115830.0
008			080604s2009 njua b 001 0 eng d
010			_a 2008024750
020			_a0132350882 _qpaperback
020			_a9780132350884 _qpaperback
040			_aDLC _beng _cDLC _dEG-CaTKH _erda
050	0	0	_aQA76.76.D47 _bC583 2009
082	0	4	_a005.1 MA.C 2009 _223
100	1		_aMartin, Robert C., _eauthor.
245	1	0	_aClean code : _ba handbook of agile software craftsmanship / _cthe Object Mentors: Robert C. Martin, Michael C. Feathers, Timothy R. Ottinger, Jeffrey J. Langr, Brett L. Schuchert, James W. Grenning, Kevin Dean Wampler, Object Mentor Inc. ; Foreward by James O. Coplien.
264		1	_aUpper Saddle River, NJ, _bPrentice Hall, _c2009.
300			_axxix, 431 pages : _billustrations ; _c24 cm.
336			_atext _btxt _2rdacontent
337			_aunmediated _bn _2rdamedia
338			_avolume _bnc _2rdacarrier
490	1		_aRobert C. Martin series
504			_aIncludes bibliographical references and index.
505	0		_aClean code -- Meaningful names -- Functions -- Comments -- Formatting -- Objects and data structures -- Error handling -- Boundaries -- Unit tests -- Classes -- Systems -- Emergence -- Concurrency -- Successive refinement -- Junit internals -- Refactoring serialdate -- Smells and heuristics.
520			_aEven 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.
650		0	_aAgile software development.
650		0	_aComputer software _xReliability.
700	1		_aCoplien, James O., _ewriter of forward.
700	1		_aFeathers, Micheal C., _eauthor.
700	1		_aOttinger, Timothy R, _eauthor.
700	1		_aLanger, Jeffrey J, _eauthor.
700	1		_aSchuchert, Brett L., _eauthor.
700	1		_aGrenning, James J., _eauthor.
700	1		_aWampler, Kevin Dean, _eauthor.
830		0	_aRobert C. Martin series.
906			_a7 _bcbc _corignew _d1 _eecip _f20 _gy-gencatlg
942			_2ddc _cBK
998			_ayomna.nassar _bP _d20230529
998			_amona.romia _bR _d20230529
999			_c260 _d260