4 ms·
Developer/Designer: so about the time adjustment. Product Manager: I'll stop you there. Thanks for your input but we don't need it for MVP as it's an infrequen
by switch007 3y ago
Developer/Designer: so about the time adjustment.
Product Manager: I'll stop you there. Thanks for your input but we don't need it for MVP as it's an infrequently used feature and having spoken to stakeholders [they didn't] and customers [they didn't], they both told me they didn't rank the clock function as important.
(PM proceeds in the rest of the meeting to question every comment and opinion the developer has as if taking part in a PhD defence, while offering zero evidence of their own assertions)
- collingreen 3y agoThis hit brutally hard. I wasn't ready for this on an otherwise peaceful Sunday morning.
- ThePowerOfFuet 3y agoViolence.
- ryandrake 3y agoDeveloper: Uh, OK then This is also why our software is so bad. Developers have no backbone and won't push back against this stuff.
- switch007 3y agoI disagree. You speak up, then the PM gets defensive, it escalates, your boss steps in and tries to defuse but ultimately agrees with the PM. So now the choice is to do what the PM decides or quit and join another company with the same set up... It's the man, man.
- whatindaheck 3y ago> This is also why our software is so bad. Developers have no backbone and won't push back against this stuff. Maybe. But I’d argue it’s more likely that people run out of energy. Or I’d rather save my energy for my personal time. PMs win unless you’re in an engineer-first company. If the hierarchy is structured to favor decisions made by those who can barely operate a microwave, why put the energy into “pushing back”?