commit d9bfcf0d532a40957aa74c397ad755ce6596b935
parent 2ae37dcffd65a7375b7ed841598d11c7716fff8a
Author: viznut_web <viznut_web@web>
Date: Mon, 27 Jun 2022 16:26:56 +0200
refactor a little
Diffstat:
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Principles.mdwn b/Principles.mdwn
@@ -22,11 +22,12 @@ Production of new computing hardware consumes a lot of energy and resources. The
Small systems are more likely to have small hardware and energy requirements, as well as high understandability. They are easier to understand, manage, [[refactor|refactoring]] and [[repurpose]].
-[[Dependencies|dependency]] (including hardware requirements and whatever external software/libraries the program requires) should also be kept low. Avoid [[pseudosimplicity]] such as user interfaces that hide their operation from the user. Scalability is essential only if there is an actual and justifiable need to scale up.
-
+* [[Dependencies|dependency]] (including hardware requirements and whatever external software/libraries the program requires) should also be kept low.
+* 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).
+* [[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!
## Hope for the best, prepare for the worst
@@ -64,11 +65,11 @@ Computers were invented to assist people in their cognitive processes. "Intellig
## Expose everything
-Make the computer visualize/auralize its internal state as well as whatever it knows about the state of its physical environment. Regard this visualization/auralization as a background landscape: facilitate observation but don't steal the attention. Also, don't use too much computing resources for this (updating a full-screen background landscape tens of times per second is a total overkill).
+As an extension of "amplify awareness": Don't hide information!
-* As an extension of "amplify awareness": Don't hide information!
* Keep everything open, modifiable and flexible.
* Share your [[source code|FLOSS]] and design philosophies.
+* **State visualization**: Make the computer visualize/auralize its internal state as well as whatever it knows about the state of its physical environment. Regard this visualization/auralization as a background landscape: facilitate observation but don't steal the attention. Also, don't use too much computing resources for this (updating a full-screen background landscape tens of times per second is a total overkill).
## Respond to changes
