You haven't heard that from me. I have fixed a lot of my own bugs as well as those made by others.
Software woes comes from at least three sources: System designers, software engineers, and users. The lion's share of trouble originates with the users.
In the beginning of a project, the systems designers grapple with the end users or user management in order to design the software system. In most cases the users do not understand their own internal data flow or their management operations. They have a terrible time articulating their needs to the system designers. System designers are pretty good at ferreting out the needs of the user; yet, they can make mistakes due to the inadequate understanding or communications on the part of the user. The system designers are less than perfect when it comes to disseminating the design to the developers. Developers do not always coordinate their work across the subsystems. User communities typically change the requirements and specifications numerous times during development, which causes havoc in the software development process, causing serious bugs to become embedded in the system.
Once a system is deployed, it becomes obvious that user management didn't really know what the ultimate users actually wanted or needed. The actual users are almost never trained.
Other than that, its a smooth process. ;-D
It seems reasonable to conclude that system designers have the opportunity to be a user and as such to figure out what the user will need. I think what the designers often do is consult with groups of people who are in positions similar to the typical user.
But again, it shouldn’t be hard for the designers to figure out the needs of the user by sitting there and working the keyboard a little. And I mean they should figure out most if not all such needs.
Another way to think of this is the quality of the product is fully the responsibility of the people making the product. It’s how the system has functioned for many centuries. Until digital technology came along. Maybe it has to do with the culture of people who become coders. I was friends with one guy who invented a product for Microsoft. Of course, he’s a brilliant guy. But he was the typical spoiled kid, a teenage hacker with intense focus who later met the right people. Many such individuals bring an attitude of entitlement to the game. I think this could have cultivated an industry-wide philosophy of “let’s milk the user.”
I don’t blame you for thinking the user needs to help design the system. I assume you’re touting the established beliefs in the industry.