The Pinocchio Problem : what defines great systems

This commit is contained in:
Morgan 2021-02-07 12:04:53 +01:00 committed by GitHub
parent be6d91e6ee
commit 8b272e9d99
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -321,6 +321,13 @@ A small group of programmers wants to change how we code—before catastrophe st
> * if you allow configuration or scripting, you give the users a way to specify the rules that must be shared, so the tool fits their systems > * if you allow configuration or scripting, you give the users a way to specify the rules that must be shared, so the tool fits their systems
> * if you want to keep the tool simple, you have to force your users to only play within the parameters that fit this simplicity > * if you want to keep the tool simple, you have to force your users to only play within the parameters that fit this simplicity
> * if your users' use cases don't map well to your simplicity, they will build shims around your tool to attain their objectives > * if your users' use cases don't map well to your simplicity, they will build shims around your tool to attain their objectives
* [Steve Yegge](https://steve-yegge.blogspot.com/2007/01/pinocchio-problem.html) - (2007) The Pinocchio Problem | Great systems :
> * should never reboot (Rebooting is Dying).
> * must be able to grow without rebooting.
> * Have a command shell.
> * Always have an extension language and a plug-in system (mods).
> * Are introspective.
> * Have to be a killer app, or they need one.
# Art :art: # Art :art:
> News > News