RSS Amplifier

Laws of Software Engineering · Jul 20, 2026

Dunning-Kruger Effect

0
Sign in to vote or save

Dr. Milan Milanović · Laws of Software Engineering

2 min read

The less you know about something, the more confident you tend to be.

Takeaways

  • Confidence without context is unreliable. Early confidence often signals ignorance, not mastery.
  • Awareness grows faster than skill. Learning initially reduces confidence, only to rebuild it.
  • Real experts speak in ranges, trade-offs, and probabilities, not with confidence about every topic.

Overview

The Dunning-Kruger Effect explains a gap between confidence and competence. When people know little about a domain, they lack the awareness required to judge their own ability. As a result, they overestimate how well they understand the problem.

As learning progresses, people discover the depth and complexity of the domain.

Awareness of unknowns grows faster than capability, leading to a drop in confidence, often called the “valley of despair.” Only after experience does confidence rise again, now with fundamental understanding.

Dunning-Kruger Effect illustration

Dunning-Kruger Effect

Examples

New developers often give confident, precise estimates, while experienced developers give ranges (the famous “it depends” answer). The juniors aren’t being careless; they simply don’t yet know what they don’t know (unknown-unknowns).

Peak enthusiasm for a new technology often comes from those who have used it least. Those with deep experience are more measured.

We should also note that Impostor syndrome reflects miscalibration in the opposite direction. Skilled individuals underestimate their competence because they are deeply aware of complexity and edge cases.

Origins

The effect was described by psychologists David Dunning and Justin Kruger in a 1999 study at Cornell University. Their experiments showed that people with low performance consistently overestimated their ability on logic, grammar, and humor tests, while high performers underestimated their ability.

The proposed mechanism is simple: the skills required to perform well are often the same skills needed to assess performance accurately.

One caveat: the original study measured how people rank themselves against peers. Low performers overestimated their relative standing, but they were not more confident than experts; the popular “peak of confidence” curve is a later simplification of the findings.

Further Reading

Want to go deeper?

All 63+ laws are covered with more depth, examples, and practical guidance in the Laws of Software Engineering book.

Get the Book

Last updated: July 20, 2026

Read the original on lawsofsoftwareengineering.com

Comments

Nothing yet. Say the first thing.

    Sign in to join the conversation.