Bug Blindness
Points and comments are a snapshot, not live.
Most developers are blind to bugs in their own software due to unconscious workarounds.
Dan Luu observes hundreds to thousands of bugs per week that most people miss, not because they don't encounter them, but because they don't notice. He argues that programmers develop unconscious habits to work around software flaws (e.g., flipping WiFi off before logging in at Microsoft, waiting before editing a Google Doc title). This 'bug blindness' means teams often ship products they believe are high quality but that normal users cannot use without non-intuitive workarounds. Luu has found that simply pointing out bugs to receptive people can cure this blindness, allowing them to see issues themselves. He cites examples like Blackboard (hated by users but loved by its developers) and Discourse (cheating on performance metrics).
What commenters are saying
The top comment distinguishes users who unconsciously adopt bug-workaround workflows from developers who remain unaware. A reply argues developers should fix software so workarounds aren't needed. Other commenters debate whether Dan Luu's own blog (lack of max-width line length) is itself a bug, with one noting the favicon markup raises an exception in browsers. A high-ranked comment shares personal experience: pointing out flaws in proposals gets one labeled as negative, so the commenter now stays quiet and prepares for failure. Two camps emerge: those who see Luu's search-quality examples as preference issues rather than bugs, and those who argue that when behavior deviates from intent, it is a bug.