Dan Luu on bug blindness
Software teams can normalize severe product-quality problems when everyone has learned invisible workarounds, so noticing bugs becomes an organizational skill.
Links: Original source · Shared link
Logged at IST: 2026-08-30 18:14 IST
What it is: Dan Luu's essay on bug blindness: the way users and builders can hit real bugs, learn workarounds, and then stop consciously noticing that anything is wrong.
Gist: Luu argues that software teams often believe a product is high quality because internal users have adapted to its flaws. They know the non-obvious sequence, the delayed title edit, the laptop wake ritual, the search workaround, or the magic incantation. A normal user sees the same thing as broken.
Dogfooding helps, but it is not enough by itself. Programmers are especially good at routing around software foibles, so they can dogfood a broken product and still miss what a fresh user would experience. The useful move is to deliberately point out issues, notice the habits people have internalized, and treat quality blindness as something that can be trained away.
The agent angle is small but important. Coding agents make it easier than ever to churn out low-quality software, but they also make it easier to improve quality once the team can actually see what needs fixing. The bottleneck becomes perception and judgment, not just implementation effort.
Newsletter angle: Useful software-quality/org-design item: the bottleneck is often not fixing bugs, but noticing the product is broken despite internal familiarity.