3 ms·
I wrote a snarky response above, but here's my non-snarky response: It's hard to answer a question phrased this way because there can be any number of reasons
by jawns 9y ago
I wrote a snarky response above, but here's my non-snarky response:
It's hard to answer a question phrased this way because there can be any number of reasons why a useful feature is not implemented. Time constraints, budget constraints, process constraints, organizational constraints ... and then somewhere in this long list is, "Gee, we just never thought about it."
Perhaps a more interesting question is:
Among those of you who believe that providing password requirements up-front is a useful feature, did you implement that feature in past projects? If not, what prevented you from doing so?
- darkerside 9y agoFor me, it's a combination of "never thought of it" and the difficult of convincing the organization it's not a security risk (yes, it sounds silly).