3 ms·
The funny thing is, developers will always have a more precise and detailed domain knowledge. Because unlike the PM, who can analyze the problem in the abstract
by ArnoVW 4y ago
The funny thing is, developers will always have a more precise and detailed domain knowledge. Because unlike the PM, who can analyze the problem in the abstract and approximate, the developer must produce working code.
However it is very difficult to have empathy with the user when you're trying to produce code. Also, you're generally judged on your ability to 'finish US' quickly. So generally you'll choose an approach 'that works'. Only to have the feedback 'great, but why did you not think about this?'
- spookthesunset 4y ago> However it is very difficult to have empathy with the user when you're trying to produce code. Not only that, but as a dev you can get into a position where what you decide to work on is based more on ease of development or “fits cleanly with what we have now”. There should be a balance. The PM should push for the impossible and the engineers can tell the PM why that won’t work. Kind of… maybe not with that much hyperbole in my assertion.
- peteradio 4y ago> the developer must produce working code. Bingo, I can't (well won't) build a contradiction even if its part of the spec. > Only to have the feedback 'great, but why did you not think about this?' Even worse IMO: "Great, no problems!" every time. Ok, I'm not that good, is anyone even running this shit?