Clean Code : A Handbook Of Agile Software Craftsmanship
Publication details: Noida: Pearson Education , 2011Description: 431ISBN:- 9788131773383
- 005.1 MAR
Item type | Current library | Collection | Call number | Status | Date due | Barcode | Item holds | |
---|---|---|---|---|---|---|---|---|
Book | Alliance College of Engineering and Design | CSE & IT | 005.1 MAR (Browse shelf(Opens below)) | Available | E11858 |
Browsing Alliance College of Engineering and Design shelves, Collection: CSE & IT Close shelf browser (Hides shelf browser)
005.1 MAL Fundamentals of Software Engineering | 005.1 MAL Fundamentals of Software Engineering | 005.1 MAL Fundamentals of Software Engineering | 005.1 MAR Clean Code : A Handbook Of Agile Software Craftsmanship | 005.1 MAT Improving Software Organizations: From Principles to Practice | 005.1 MAT Software Engineering | 005.1 MAT Software Engineering |
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.
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.
There are no comments on this title.