The author has missed something vital (and to be fair while HN might not be the right demographic for arguing it I think most of us understand it intrinsically)

The author has missed something vital (and to be fair while HN might not be the right demographic for arguing it I think most of us understand it intrinsically): The difference between and inconvenience and a barrier is typically in the knowledge level of the user. For example years ago I found that I understood how devs built enough to know all the common UI/UX patterns. If I needed to get to some buried functionality out of a piece of software I wasn’t familiar with I could usually find the control in less than 3 seconds whether it was a tiny button or a menu item 4 layers deep. But hand that same task to a user without the experience needed to reach that level of understanding, and that becomes a barrier that can slow them down or halt them entirely. And here’s the issue: usually those are your ideal customers. The ones you’re building for, the ones that pay you, and the ones that you want to sing the praises of your software. TL;DR: Keep your perspective in check when developing: is it a “papercut” because it’s insignificant to everyone? Or because you have thick skin?