4 ms·

I agree. I've also noticed that some developers seem to have a strong sense of "we should not do that" while others don't and I'm not sure why. One recent exam

by _wldu 5y ago

I agree. I've also noticed that some developers seem to have a strong sense of "we should not do that" while others don't and I'm not sure why. One recent example was impersonating/spoofing a manager's email to send phishing emails as part of a security compliance test. One developer saw no harm at all in doing so while another felt we should ask permission first. It's a basic violation of trust to do this sort of thing and in the very least, permission should be obtained first. Otherwise, the violation of trust and repercussions may be severe.

bmhin 5y ago
As someone who naturally gets feelings of aversion when I hear some solutions suggested and who works with folks who can suggest them without blinking, I honestly think "should" never enters their mind. It seems to be a pure engineering-in-a-vacuum mindset where "can" is all that matters. They envision an admittedly potentially interesting end outcome and the means to get there is just engineering. They don't think twice about how their solution just involved enabling tracking everyone's phone's location to enable it. My and many others first thought would likely be "I don't really want to be tracked myself or have to track others" and all they think of is "We can dynamically allocate the resources based on where people are!".