From 6d40dc7f65620d8fa755c1ffd84695fa4c46ac49 Mon Sep 17 00:00:00 2001 From: Artem Zakirullin Date: Thu, 26 Sep 2024 07:25:49 +0300 Subject: [PATCH] fix wording --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 179a693..5e206da 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ We should reduce the cognitive load in our projects as much as possible. The tricky part is that the author may not have experienced a high cognitive load due to familiarity with the project.
- Familiarity vs Simplicity + Familiarity vs low cognitive load
The problem is that familiarity is not the same as simplicity. They feel the same — that same ease of moving through a space without much mental effort — but for very different reasons. Every “clever” (read: “self-indulgent”) and non-idiomatic trick you use incurs a learning penalty for everyone else. Once they have done that learning, then they will find working with the code less difficult. So it is hard to recognise how to simplify code that you are already familiar with. This is why I try to get “the new kid” to critique the code before they get too institutionalised!

It is likely that the previous author(s) created this huge mess one tiny increment at a time, not all at once. So you are the first person who has ever had to try to make sense of it all at once.