From 71bf9dce4604c5b97f8f0f30a3073f51902b8e57 Mon Sep 17 00:00:00 2001 From: Jim Collins Date: Thu, 28 Nov 2024 12:28:15 -0500 Subject: [PATCH] Update narrow-conduits.md Changed "As stated in [our announcemnt](/blog/open-source-announcement)" to "As stated in [our announcement](/blog/open-source-announcement)" fixing typo in "announcemnt" --- blog/narrow-conduits.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/narrow-conduits.md b/blog/narrow-conduits.md index 2f4b9394..9c2a2cbf 100644 --- a/blog/narrow-conduits.md +++ b/blog/narrow-conduits.md @@ -1,7 +1,7 @@ # Narrow Conduits and the Application-Platform Interface ###### 12 Nov, 2024 ### [Vish Abrams](https://github.com/vishvananda) -![Vish Abrams](/images/bios/vish.jpg) Welcome to the twelve-factor maintainters blog. As stated in [our announcemnt](/blog/open-source-announcement), some of our posts will analyze the manifesto more generically. This is the first post in that vein, where we dive into the interface between the application and the platform. +![Vish Abrams](/images/bios/vish.jpg) Welcome to the twelve-factor maintainters blog. As stated in [our announcement](/blog/open-source-announcement), some of our posts will analyze the manifesto more generically. This is the first post in that vein, where we dive into the interface between the application and the platform. It is well understood that defining a clear contract between parts of a system allows one to shed cognitive load on either side of the contract. This has been called the "narrow-waist" principle which has some unfortunate connotations, so we'll refer to it as the "narrow-conduit" principle. This principle is especially valuable when the humans on either side of the conduit have dramatically different concerns.