Design principles: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
Line 5: | Line 5: | ||
*[[Have excellent data]] | *[[Have excellent data]] | ||
*[[Automation eliminates value but not risk]] | *[[Automation eliminates value but not risk]] | ||
*[[Solve simple problems]]. Leave the hard stuff to the experts. | *[[Solve simple problems]]. Like [[Blind spot assistance]]. Leave the hard stuff to the experts. | ||
===Antifragile=== | ===Antifragile=== | ||
*[[Be sceptical of models]] ↔ [[Don’t tick boxes]] ↔ watch out for proxies. Don't confuse simplistic models with simplicity. | *[[Be sceptical of models]] ↔ [[Don’t tick boxes]] ↔ watch out for proxies. Don't confuse simplistic models with simplicity. | ||
*[[Decomplicate]] ↔ [[reduce complexity]]: do few things well, rather than everything fairly. | *[[Decomplicate]] ↔ [[reduce complexity]]: do few things well, rather than everything fairly. | ||
*[[Be antifragile]] | *[[Be antifragile]] | ||
{{sa}} | |||
*[[Blind spot assistance]] |
Revision as of 17:20, 10 August 2020
|
- Know your purpose
- Amplify signal, minimise noise
- Know your client ↔ Be personal
- Have excellent data
- Automation eliminates value but not risk
- Solve simple problems. Like Blind spot assistance. Leave the hard stuff to the experts.
Antifragile
- Be sceptical of models ↔ Don’t tick boxes ↔ watch out for proxies. Don't confuse simplistic models with simplicity.
- Decomplicate ↔ reduce complexity: do few things well, rather than everything fairly.
- Be antifragile