aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes/tech/about-apis.gmi
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2026-07-04 14:07:02 +0200
committeralex <alex@pdp7.net>2026-07-04 14:07:02 +0200
commitad007d8e4b6cd904382841337ece86dd744c9240 (patch)
treec135e84f35ee6a0f5bec11ca9a962c502e8a33b3 /blog/content/notes/tech/about-apis.gmi
parentcca2fda91a57bb237295f963c61a350cc8b88151 (diff)
Add /notes/tech/modularity, link it to /notes/tech/about-apismaster
Diffstat (limited to 'blog/content/notes/tech/about-apis.gmi')
-rw-r--r--blog/content/notes/tech/about-apis.gmi4
1 files changed, 4 insertions, 0 deletions
diff --git a/blog/content/notes/tech/about-apis.gmi b/blog/content/notes/tech/about-apis.gmi
index f1732cc9..7f604a2c 100644
--- a/blog/content/notes/tech/about-apis.gmi
+++ b/blog/content/notes/tech/about-apis.gmi
@@ -24,3 +24,7 @@ We propose that the architecture benefits of level 4 are also present in levels
Note also that level 3 can provide many benefits of level 4, but with less development overhead, so it's a level we recommend considering explicitly, as it is often overlooked.
Level -oo is typical of legacy applications. Note that we consider the distance between level -oo and the rest of levels much bigger than the distance between the rest of levels.
+
+## Further reading
+
+=> ./modularity Modularity