Skip to content
0:00 / 0:00

#modelarity#cleancode#kevlinhenney

Why Your Code Feels Wrong (Kevlin Henney on Modelarity)

Dev Tools Made Simple

25K subscribers • 16 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

7.5K views1 year ago2 recommendations

Software designTools and practiceDesign patternsSoftware architectureSimplicity and complexity

An explanation of modelarity and how aligning code with a developer's mental model reduces cognitive load.

#CleanCode #KevlinHenney #WardCunningham #SoftwareDesign #MentalModels #CodeReview #SoftwareEngineering #ProgrammingPhilosophy #CodeReadability #DeveloperLife #CodeRefactoring #CognitiveLoad #Modularity #CodeSmells #DevToolsMadeSimple Boost your coding skills by joining Scrimba: scrimba.com?via=DevToolsMadeSimple In this video, Kevlin Henney introduces the concept of modelarity — not to be confused with modularity — as a key trait of good code. He explains how great code mirrors the developer's mental model of the problem, and why breaking that alignment increases cognitive load. Ward Cunningham, inventor of the Wiki and pioneer of extreme programming, echoes this idea with his classic take on clean code: it's the kind of code where each routine is exactly what you expected. No surprises. No mental gymnastics. I break down how these ideas connect and why closing the gap between thought and implementation can free up your most valuable resource as a developer: your brainpower. Sources: youtu.be/h-X7JhU3hI0?si=U_stiEzA1eGCUk2p youtu.be/7EmboKQH8lM?si=OR8yYIQPI9EaHAGh

Why it's here

2 people recommend this

What people say. Recommended as a conceptual explanation of how code should match the developer's mental model.

u/Budget_Putt8393in r/programming • Recommends

On “AI coding agents didn't misunderstand you. They just fill the blank you left.”

And when you have fully described the what and the how, ***you have written the code.*** Same argument has come up with UML, and other requirements/design documentation efforts. Docs need to describe the processing model, the code needs to faithfully implement so maintenance is possible. YouTube - why your code feels wrong AI sucks at this.

u/MinimumMagician5302in r/softwarearchitecture • Recommends

Why Your Code Feels Wrong (Kevlin Henney on Modelarity)