commit a9c342e2ab063aef87b87915719244552c03351a
parent 52a12505ebf7aed3f5bd120c62c938b3c37bbbc5
Author: ola <ola@web>
Date: Mon, 9 Jun 2025 20:10:12 +0200
empty web commit
Diffstat:
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/build_on_solid_ground.mdwn b/build_on_solid_ground.mdwn
@@ -1,5 +1,5 @@
-Consider when to build on solid ground and when to design for disappearance. If
-longetivity is required some considerations are needed.
+Consider when to build on solid ground and when to design for disappearance.
+Longevity requires some considerations.
Many computing systems are based on platforms, frameworks or even languages
that change very rapidly, may become obsolete at any time, and are too complex
@@ -20,18 +20,19 @@ What can YOU do
**With or without a computer**
-* Consider using software that runs locally, is open-sourced, and has a thriving user community or is well-documented
+* Consider using software that runs locally, is open-sourced, and has a thriving user community, or is well-documented
* Try to pick software that favours slow release cycles and thorough testing over rolling updates.
-* try to use smaller, more general-purpose tools instead of complex, prescriptive all-in-one solutions
+* Try to use smaller, more general-purpose tools instead of complex, prescriptive all-in-one solutions
* You may also read this as "grow roots to a solid ground". Learn things that last. Learn the history of the technology you use.
**When creating and maintaining software, digital tools or infrastructure**
* Avoid unreliable dependencies, especially those hard (non-optional) dependencies. If you can't work around them (in case of software), you can’t avoid using such dependencies, you should bundle them directly with your software keep local copies, instead of relying on downloading them from external servers every time. This way, your software won’t break if those external resources disappear.
-* It is possible to support several target platforms. In case of lasting programs, one of these should be a bedrock platform, or instruction set, that does not change too much and therefore increase accessibility, portability and fallback scenarios.
+* It is possible to support several target platforms. In case of lasting programs, one of these should be a bedrock platform, or instruction set, that does not change too much and therefore increases accessibility, portability, and fallback scenarios.
* Imagine some of your users will never be able to get an update or find support - think about how they might solve their problems.
-* Try to use standard file and data exchange formats, ideally formats that are human-readable. * Don't take anything for granted. Especially don't expect the infrastructure such as the power grid and global networking to continue working indefinitely.
+* Try to use standard file and data exchange formats, ideally formats that are human-readable.
+* Don't take anything for granted. Especially don't expect the infrastructure, such as the power grid and global networking, to continue working indefinitely.
Principle in action
