Chapter 3

1. We can place our code in individual source files in folder structures and wrap classes, interfaces, structs, and enums in namespaces that map to the folder structure.
2. A class should have only one responsibility.
3. You can comment in your code for document generators using XML comments placed directly above the public member to be documented.
4. Cohesion is the logical grouping together of code that works on the same responsibility.
5. Coupling refers to the dependencies between classes.
6. Cohesion should be high.
7. Coupling should be low.
8. You can use DI and IoC to design for change.
9. DI stands for Dependency Injection.
10. IoC stands for Inversion of Control.
11. Immutable objects are type-safe and so can be safely passed between threads.
12. Objects should expose methods and properties and hide data.
13. Data structures should expose data and have no methods.
...