commit 7b8a90c9b0438eefdc00778d932ed2609605f083
parent fa21e2fc9296cf912c9f56d59ceddab3c93395a4
Author: ola <ola@web>
Date: Fri, 6 Jun 2025 11:10:08 +0200
empty web commit
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/principles2.mdwn b/principles2.mdwn
@@ -247,7 +247,7 @@ With or without a computer:
* 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.
+ * Avoid unreliable dependencies, especially those hard (non-optional) dependencies. If you can't work around them (in case of software), 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.
* 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.
