4 ms·
The products I work on, I know which customers are asking for which features. I also hear from the managers and BAs why features are requested. It's not a stret
by throwaway55554 7y ago
The products I work on, I know which customers are asking for which features. I also hear from the managers and BAs why features are requested. It's not a stretch to assume the developers in question knew what they were adding and who for. And at the very least they could intuit why.
What's really hard to imagine is developers implementing features without understanding what they're implementing.
Not saying they alone should be thrown under the bus, but shame on them!
- vsareto 7y agoSo the BAs and managers know too, and a typical assumption is that they know before they ever talk to a developer. They have every opportunity to reject it themselves on ethical grounds before they ever talk to a developer. And yet, they still bring this known-ethically-bad feature to the developer and ask them to implement it! If devs are talking and developing customer needs directly (a legitimate thing), then that is a situation where developers are the first ones who should be pushing back. But in companies where there are multiple layers before a feature reaches a developer? Devs should not be the ethical enforcement.
- throwaway55554 7y ago> Devs should not be the ethical enforcement. Yes, they should. If nobody else does, they're the last in line and they should remain ethical. "Nobody else stopped the feature" is NOT AN EXCUSE.
- vsareto 7y agoNo, people above devs should be ethical enforcement, before devs Devs can be, if they have to be, but they shouldn't If it reaches the dev, there should be greater consequences for not catching it earlier.