Clean Code: A Handbook of Agile Software Craftsmanship
Pearson Education, 1 de ago de 2008 - 464 páginas
Even 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
O que estão dizendo - Escrever uma resenha
Não encontramos nenhuma resenha nos lugares comuns.
Objects and Data Structures
Smells and Heuristics
Cross References of Heuristics
Outras edições - Visualizar todos
The Robert C. Martin Clean Code Collection (Collection)
Robert C. Martin
Visualização de trechos - 2011
abstract class Agile Software Development algorithm APRIL argChar Args Args.java argument ArgumentMarshaler AspectJ assertEquals BooleanArgumentMarshaler booleanValue byte-code catch ArgsException clean code concurrent constant create currentArgument day-of-the-week duplication elementId enum error errorArgumentId errorCode errorParameter example final String FitNesse function IllegalArgumentException implementation import instanceof integer IntegerArgumentMarshaler interface Java Javadoc JUnit Kent Beck Law of Demeter level of abstraction lines marshalers.put(elementId method module month null object package param parameter private boolean private int private Map<Character private static private String private void problem production code public abstract public boolean public class public int public public public public static final public String public void refactored return true SerialDate Single Responsibility Principle SpreadsheetDate static final int StringArgumentMarshaler stringToMonthcode stringToweekdayCode stringValue suffixLength Test-Driven Development things threaded code threads throw new ArgsException throws ArgsException throws Exception unit tests variables write