vault backup: 2025-01-17 09:53:17
This commit is contained in:
@@ -128,8 +128,9 @@ Principle of least knowledge.
|
||||
a.b().c() breaks the law --> violates coupling
|
||||
a.b() doesn't break the law
|
||||
|
||||
### Design to Invariants, Design
|
||||
Product Families: attack different target markets with different value propositions with the same base platform: (pickup truck and suv example. For ford it's the same car (slight difference in build but 95% the s))
|
||||
### Design for Invariants, Design for Change
|
||||
Product Families: attack different target markets with different value propositions with the same base platform: (pickup truck and suv example. For ford it's the same car (slight difference in build but 95% the same)).
|
||||
Core of the software design is made for the invariants, meaning all the things that do not change and are the same throughout the software. An example might be the base driver code and the base I2C/SPI interface, which all the drivers use. Every driver
|
||||
|
||||
---
|
||||
## Exercises
|
||||
|
||||
Reference in New Issue
Block a user