A philosophy of software design / John Ousterhout.
Material type:![Text](/opac-tmpl/lib/famfamfam/BK.png)
- 1732102201
- 9781732102200
- 005.12 23
- O988 2018
Item type | Current library | Call number | Status | Date due | Barcode |
---|---|---|---|---|---|
General Lending | Carlow Campus Library General Lending | 005.12 (Browse shelf(Opens below)) | Checked out | 27/08/2020 | 85359 |
Browsing Carlow Campus Library shelves, Shelving location: General Lending Close shelf browser (Hides shelf browser)
Includes index.
CW207
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