That's not exactly the point TFA is making but I want to point out that I vastly prefer when people tell me "X is broken/bad/doesn't work/weird/..." rather than

That's not exactly the point TFA is making but I want to point out that I vastly prefer when people tell me "X is broken/bad/doesn't work/weird/..." rather than "maybe you should change it to do Y instead". Mainly because the vast majority of the time "Y" is worthless garbage, and then I have to spend time explaining why I'm not going to do "Y" because I don't want you to think I'm just not valuing your output. For a simple but very common example, take videogames. Players will readily tell you when some aspect of your game is broken, when it's too easy or too grindy or too random or too unfair etc... That's valuable feedback. On the other hand when you read gaming forums and see the "fixes" the player propose, a vast majority of the time it's completely missing the mark. Either because they're not developers so they don't realize the complexity of what they're proposing, or they're simply not game designers and they don't realize all the new problems their solution would create, or they're hardcore players and their tweaks would make the game unplayable for the 99% of casual base etc... In my experience this is almost always true. I always listen to the feedback I get for my software, but I tend to immediately dismiss the "maybe you could do Y instead" part. I know the entirety of the problem space, the user doesn't. The user has a specific use case in mind but I know that there are hundreds of other clients who don't use the program exactly the way this one person does. So unless you're actually going to write some code for me I'd much rather you'd give me precise criticisms and feedback on your experiences than trying to explain how you think it should be done.