# Ted Kaminski - System boundaries: the focus of design (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/38422217) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Ted Kaminski]] **Full Title**:: System boundaries: the focus of design **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [www.tedinski.com](https://www.tedinski.com/2018/02/06/system-boundaries.html) **Host**:: [[www.tedinski.com]] **Highlighted**:: [[2024-03-06]] **Created**:: [[2024-03-08]] ## Highlights - Since we’re embracing an approach where some design fixes can be put off until later, what should we prioritize to fix sooner? The quick answer is: anything that’s difficult to change later. ([View Highlight](https://read.readwise.io/read/01hr9y32dn7wwrp4v9e93ev0sz)) ^688860182 - But while introducing boundaries has its re-use benefits, it also introduces costs. Changes cannot be easily made anymore. ([View Highlight](https://read.readwise.io/read/01hr9y5f6me3exz8c08chvcx9d)) ^688860518