From 1fbb1bfb939163ffbeb094ea81b13305751aa001 Mon Sep 17 00:00:00 2001 From: maxmwang Date: Mon, 16 Dec 2024 15:22:07 -0800 Subject: [PATCH] quick edit --- docs/src/core/infrastructure/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/core/infrastructure/README.md b/docs/src/core/infrastructure/README.md index b2f224867..cde0f3c53 100644 --- a/docs/src/core/infrastructure/README.md +++ b/docs/src/core/infrastructure/README.md @@ -15,4 +15,4 @@ Welcome to the infrastructure section. Software infrastructure refers to the services and tools that create an underlying layer of abstractions that the application is developed on. Compared to the application layer, infrastructure is significantly more broad in its responsibilities, although these responsibilities are more common in software development. > [!IMPORTANT] -> We aim to use a **small** set of **existing** solutions with large communities. This philosophy reduces the [cognitive load](https://thevaluable.dev/cognitive-load-theory-software-developer/) on each developer and simplifies the onboarding process. This approach is valuable for creating long-lasting software, especially when our developers are cycled out after only ~4 years. +> We aim to use a **small** set of **existing** infrastructure solutions with large communities. This philosophy reduces the [cognitive load](https://thevaluable.dev/cognitive-load-theory-software-developer/) on each developer and simplifies the onboarding process, both of which are valuable for creating long-lasting software in a team where developers are typically cycled out after only ~4 years.