From a4d1b69e0c380071f098f2566e78937c47205033 Mon Sep 17 00:00:00 2001 From: Curtis Gibby Date: Fri, 7 Feb 2020 10:47:43 -0700 Subject: [PATCH] =?UTF-8?q?Update=20name=20of=20Dunning=E2=80=93Kruger=20e?= =?UTF-8?q?ffect?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- content/guides/levels-of-seniority.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/guides/levels-of-seniority.md b/content/guides/levels-of-seniority.md index 38e37f9e1..a621ebe28 100644 --- a/content/guides/levels-of-seniority.md +++ b/content/guides/levels-of-seniority.md @@ -19,7 +19,7 @@ Junior developers are normally fresh graduates and it's either they don't have o * Over-engineering is a major problem, often leading to fragility and bugs. * When given a problem, they often try to fix just the current problem a.k.a. fixing the symptoms instead of fixing the root problem. * You might notice the "[Somebody Else's Problem](https://en.wikipedia.org/wiki/Somebody_else%27s_problem)" behavior from them. -* They don't know what or how much they don't know, thanks to [Dunning Kruger Effect](https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect). +* They don't know what or how much they don't know, thanks to the [Dunning–Kruger effect](https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect). * They don't take initiatives and they might be afraid to work on an unfamiliar codebase. * They don't participate in team discussions.