commit 7938bc970ed42274e5962b42e8eda4759750bf17
parent 9a02b75b3ed7efa1a484f596680adebf0c67272b
Author: neau <neau@web>
Date: Sun, 3 Jul 2022 19:42:17 +0200
empty web commit
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Principles.mdwn b/Principles.mdwn
@@ -26,7 +26,7 @@ Small systems are more likely to have small hardware and energy requirements, as
* Avoid [[pseudosimplicity]] such as user interfaces that hide their operation from the user.
* **Accumulate wisdom and experience rather than codebase**.
* **Low complexity is beautiful**. This is also relevant to e.g. visual media where "high quality" is often thought to stem from high resolutions and large bitrates.
-* **Human-sized computing**: a reasonable level of complexity for a computing system is that it can be entirely understood by a single person (from the low-level hardware details to the application-level quirks).
+* [[Human-scale]]: a reasonable level of complexity for a computing system is that it can be entirely understood by a single person (from the low-level hardware details to the application-level quirks).
* [[Scalability]] (upwards) is essential only if there is an actual and justifiable need to scale up; down-scalability may often be more elevant.
* **Abundance thinking**. If the computing capacity feels too limited for anything, you can rethink it from the point of view of abundance (e.g. by taking yourself fifty years back in time): tens of kilobytes of memory, thousands of operations per second – think about all the possibilities!
