Don't confuse Readability with Familiarity
summary
Claims that readability versus familiarity are different, backed by quick experiments: bootcamp students overwhelmingly prefer fat‑arrow syntax while experienced critics favor older forms, and studies exposing people to hieroglyphs/Chinese characters show prior exposure boosts positive ratings (familiarity bias). Argues there is no industry "ACT" for code‑reading comprehension, pushes measurable questions like “does this clarify or obscure?”, defends functional patterns and nested ternaries when their grammar is understood, and recommends isolating impact, teaching, and asking data‑driven questions. familiar to whom
AI-written summary · about
chapters (17)
- 0:00Introduction and context
- 1:07Why this talk matters
- 2:08Defining readability
- 3:34Readability vs complexity
- 6:03What makes code readable
- 9:21Familiarity vs readability
- 11:52Familiarity bias in code
- 14:01Familiar to whom
- 16:07Familiarity bias experiments
- 18:13Overcoming familiarity bias
- 20:43Practical advice for authors
- 22:48Airing grievances
- 23:30Functional programming bias
- 24:35Nested ternaries debate
- 25:37Whitespace and prettier
- 25:58Key takeaways
- 27:03Further reading and Q&A
