A Philosophy of Software Design
Book information
Description
The nature of complexity -- Working code isn't enough -- Modules should be deep -- Information hiding (and leakage) -- General-purpose modules are deeper -- Different layer, different abstraction -- Pull complexity downwards -- Better together or better apart? -- Define errors out of existence -- Design it twice -- Why write comments? The four excuses -- Comments should describe things that aren't obvious from the code -- Choosing names -- Write the comments first -- Modifying existing code -- Consistency -- Code should be obvious -- Software trends -- Designing for performance.
Similar books
Computer Architecture
2011 · PDF
Architecture and Patterns for IT Service Management, Resource Planning, and Governance: Making Shoes for the Cobbler's Children
2011 · EPUB
Clean Architecture: a Craftsman's Guide to Software Structure and Design
2017 · PDF
Clean Architecture: a Craftsman's Guide to Software Structure and Design
EPUB
Clean Architecture A Craftsman's Guide to Software Structure and Design-Pearson Education
EPUB
Software Architecture in Practice
EPUB
Agile Software Architecture
2013 · PDF