3 ms·
Are they really that smart if they’re ignoring those things? Talking to users has always been on my list of things required for engineers. A decade+ of low-int
by breckenedge 3y ago
Are they really that smart if they’re ignoring those things? Talking to users has always been on my list of things required for engineers.
A decade+ of low-interest-rate fueled growth in the tech sector has meant a lot of us have succeeded just by showing up.
- twoodfin 3y agoIn my experience, close technical customer-developer collaboration is incredibly valuable. What’s not great is customers arguing with engineers about which features to implement first or whether their bug report ought to have been backlogged. This is where a strong product role is essential.
- breckenedge 3y agoI agree. Have the product team facilitate communications between customers and engineers and guide efforts towards development that has the biggest returns. Sadly I don’t really ever see it functioning that way anymore.
- crazygringo 3y ago> Talking to users has always been on my list of things required for engineers. For any product of reasonable complexity, taking to users is something a PM should be spending ~1.5 days/wk on. Plus overseeing quantitative user research. If your engineers are all spending that kind of time on users, that's slowing down the amount of time writing software by a huge amount.
- esafak 3y agoIn big companies there is not even a way for engineers to reach out to users. They come to you through feedback.