4 ms·
that's assuming you have somewhat cooperative people, in which case I don't think it's a setup to fail situation. my reading of it was more like some past expe
by gryn 3y ago
that's assuming you have somewhat cooperative people, in which case I don't think it's a setup to fail situation.
my reading of it was more like some past experience where I tried to do what you described only to be reprimanded for "overstepping boundaries" and that not being my job function, especially when the manager/PO/etc insist on being an exclusive gateway to information despite repeatedly failing to do that job correctly.
I think we all agree on the importance on your last part where you need to suss out whether they want an obedient code monkey or someone to solve the problem. probably through an iterative dialog where the parties involved get to explore and update their understanding of the problem, the technical and non technical constraints and the solution space.
- robocat 3y ago> especially when the manager/PO/etc insist on being an exclusive gateway to information A strong signal to leave a sinking ship. I suspect even if you somehow pull a rabbit out of the bag you wouldn't be rewarded for it. I stuck with one project like that when I shouldn't: I finished the work however the useless salesperson was screwing up the communications with the client and didn't get the project across the line to them. One of the most demotivating environments to suffer.
- whstl 3y agoThis 100%. This siloing is what causes fear and uncertainty about project, and also what makes developers atrophy their "talk to users" muscle. It is what made me leave jobs in the past and made me fight to change how things work at my current job.