Clean Code : A Handbook Of Agile Software Craftsmanship (Record no. 45161)

MARC details
000 -LEADER
fixed length control field 01927 a2200169 4500
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9788131773383
082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 005.1 MAR
100 ## - MAIN ENTRY--PERSONAL NAME
Personal name Martin, Robert C
245 ## - TITLE STATEMENT
Title Clean Code : A Handbook Of Agile Software Craftsmanship
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT)
Name of publisher, distributor, etc Pearson Education
Place of publication, distribution, etc Noida
Date of publication, distribution, etc 2011
300 ## - PHYSICAL DESCRIPTION
Extent 431
520 ## - SUMMARY, ETC.
Summary, etc ven 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.<br/><br/>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.<br/><br/>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.<br/><br/>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 ## - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Clean Code
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Encoding
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Functions
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Koha item type Book
Source of classification or shelving scheme Dewey Decimal Classification

No items available.