代码整洁之道

[rogerxu]

代码整洁之道 (豆瓣)

• [x] Chapter I: Clean Code
  • [x] There Will Be Code
  • [x] Bad Code
  • [x] The Total Cost of Owning a Mess
  • [x] The Grand Redesign in the Sky
  • [x] Attitude
  • [x] The Primal Conundrum
  • [x] The Art of Clean Code?
  • [x] What Is Clean Code?
  • [x] Schools of Thought
  • [x] We Are Authors
  • [x] The Boy Scout Rule
  • [x] Prequel and Principles
  • [x] Conclusion
  • [x] Bibliography
• [x] Chapter 2: Meaningful Names
  • [x] Introduction
  • [x] Use Intention-Revealing Names
  • [x] Avoid Disinformation
  • [x] Make Meaningful Distinctions
  • [x] Use Pronounceable Names
  • [x] Use Searchable Names
  • [x] Avoid Encodings
  • [x] Hungarian Notation
  • [x] Member Prefixes
  • [x] Interfaces and Implementations
  • [x] Avoid Mental Mapping
  • [x] Class Names
  • [x] Method Names
  • [x] Don't Be Cute
  • [x] Pick One Word per Concept
  • [x] Don't Pun
  • [x] Use Solution Domain Names
  • [x] Use Problem Domain Names
  • [x] Add Meaningful Context
  • [x] Don't Add Gratuitous Context
  • [x] Final Words
• [ ] Chapter 3: Functions
  • [x] Small!
  • [x] Blocks and Indenting
  • [x] Do One Thing
  • [x] Sections within Functions
  • [x] One Level of Abstraction per Function
  • [x] Reading Code from Top to Bottom: The Stepdown Rule
  • [x] Switch Statements
  • [x] Use Descriptive Names
  • [x] Function Arguments
  • [x] Common Monadic Forms
  • [x] Flag Arguments
  • [x] Dyadic Functions
  • [x] Triads
  • [x] Argument Objects
  • [x] Argument Lists
  • [x] Verbs and Keywords
  • [x] Have No Side Effects
  • [ ] Output Arguments
  • [ ] Command Query Separation
  • [ ] Prefer Exceptions to Returning Error Codes
  • [ ] Extract Try/Catch Blocks
  • [ ] Error Handling Is One Thing
  • [ ] The Error. java Dependency Magnet
  • [ ] Don't Repeat Yourself
  • [ ] Structured Programming
  • [ ] How Do You Write Functions Like This?
  • [ ] Conclusion
  • [ ] Setup Teardown Includer
  • [ ] Bibliography
• [ ] Chapter 4: Comments
  • [ ] Comments Do Not Make Up for Bad Code
  • [ ] Explain Yourself in Code
  • [ ] Good Comments
  • [ ] Legal Comments
  • [ ] Informative Comments
  • [ ] Explanation of Intent
  • [ ] Clarification
  • [ ] Warning of Consequences
  • [ ] TODO Comments
  • [ ] Amplification
  • [ ] Javadocs in Public APIs
  • [ ] Bad Comments
  • [ ] Mumbling
  • [ ] Redundant Comments
  • [ ] Misleading Comments
  • [ ] Mandated Comments
  • [ ] Journal Comments
  • [ ] Noise Comments
  • [ ] Scary Noise
  • [ ] Don't Use a Comment When You Can Use a
  • [ ] Function or a Variable
  • [ ] Position Markers
  • [ ] Closing Brace Comments
  • [ ] Attributions and Bylines
  • [ ] Commented-Out Code
  • [ ] HTML Comments
  • [ ] Nonlocal Information
  • [ ] Too Much Information
  • [ ] Inobvious Connection
  • [ ] Function Headers
  • [ ] Javadocs in Nonpublic Code
  • [ ] Example
  • [ ] Bibliography
• [ ] Chapter 5: Formatting
  • [ ] The Purpose of Formatting
  • [ ] Vertical Formatting
  • [ ] The Newspaper Metaphor
  • [ ] Vertical Openness Between Concepts
  • [ ] Vertical Density
  • [ ] Vertical Distance
  • [ ] Vertical Ordering
  • [ ] Horizontal Formatting
  • [ ] Horizontal Openness and Density
  • [ ] Horizontal Alignment
  • [ ] Indentation
  • [ ] Dummy Scopes
  • [ ] Team Rules
  • [ ] Uncle Bob's Formatting Rules
• [ ] Chapter 6: Objects and Data Structures
  • [ ] Data Abstraction
  • [ ] Data/Object Anti-Symmetry
  • [ ] The Law of Demeter
  • [ ] Train Wrecks
  • [ ] Hybrids
  • [ ] Hiding Structure
  • [ ] Data Transfer Objects
  • [ ] Active Record
  • [ ] Conclusion
  • [ ] Bibliography