4 ms·
The description of the "problem" is that the requirements specified in the beginning were wrong, and then the developer is blamed for solving exactly what was s
by jseban 5y ago
The description of the "problem" is that the requirements specified in the beginning were wrong, and then the developer is blamed for solving exactly what was specified, and not constantly asking management every day "have you changed your mind?". I don't understand at all, how this is the fault of the developer, talk about expecting the developer to bend over backwards for any product manager. How is it not reasonable for management/PO to be responsible for 1. sending devs off in the wrong direction, and 2. not notifying them as requirements change?
This is just another way of saying "management is right, even when they're wrong, and you need to accept that".
- Jabbles 5y agoNon-trivial problems often require exploration of the solution space. You're not expected to ask management if they've changed their mind, you're meant to present your finding so far, and ask if they have any feedback. Simply stating that you did as instructed is not a viable excuse for a human, that's not what they're paying you for. Computers can get away with it.
- jseban 5y ago> Simply stating that you did as instructed is not a viable excuse for a human, that's not what they're paying you for. Getting paid for doing what someone tells you to do, is literally the definition of a job. What you're saying actually, is that it's not your job to do your job, it's your job to also do the managers/PO's job.
- Jensson 5y agoYou also get paid to be the scapegoat for when your manager fails to do his job, like in this story.