- How to use this book
- the best way to use this book is in conjunction with code reviews when you read other people’s code, think about whether it conforms to the concepts discussed here and how that relates to the complexity of the code.
mindmap - A Philosophy Of Software Design - POSD
Content
- POSD - complexity in software design
- POSD - strategic vs tactical programming
- POSD - modules should be deep
- POSD - information hiding and information leakage
- POSD - general purpose modules vs special purpose modules
- POSD - different layer different abstraction
- POSD - pull complexity downwards
- POSD - better together or better apart
- POSD - define errors out of existence
- POSD - design it twice
- POSD - why write comments
- POSD - how to write better comments
- POSD - choosing names
- POSD - write comments first
- POSD - modifying existing code
- POSD - consistency
- POSD - could be more obvious