Comments by "yapdog" (@yapdog) on "Fighting User Requirements That CONSTANTLY Change" video.

Users have general ideas about what they want, but specific ideas about what they don't want.
17
If you are not a user of your own software, you will never truly understand your users.
9
@ContinuousDelivery True. Another approach is to flip the script: users develop the software. It's been my experience that most developers tend to believe they're smarter than the users. However, disciplines may require technical knowledge but they don't define smarts: it's highly likely that there are users of any sw that are "smarter" than the people who developed it. At least that's what I intend to find out with my platform. If I'm right, you, Dave, will likely want to interview me ~2 years from now. If I'm wrong.... we will never speak of this! 😅 (but I'm not wrong)
1
@haxwithaxe True enough. However, if you're not a user there is very little chance of you ever relating to the diversity within your base. Conversely, if you're a user, then you will be able to relate to said diversity. You just need to define what being a user means to you: are you locked in on one workflow or use, or are you open to discovering new workflows and uses for the products you create?
1
@ContinuousDelivery For clarity's sake, for what types of projects is it not possible?
1
@phoenix-walker Projects for military are whole different beasts, because the client/users are more... disciplined (i.e. requirements tend to be well defined, and they require organizations to have processes in place for product management). I never handled any defense/government projects myself, but I used to work for Bell Labs backinnaday, so I'm vaguely familiar with them.
1
@antdok9573 Actually, this one is possible. You don't code such a system blind; it requires a UI. U it.
1