emarkp wrote:We had Stake Conference + General Conference right after some of our people changed passwords, and caused quite a conundrum Sunday.
So are you saying that your users were prompted to change their passwords, changed their passwords, and then forgot the new passwords because they didn't have to use them for three weeks, which prevented them from logging in? Or was there some other error that prevented them from logging in?
emarkp wrote:So decreasing security and causing inconvenience is okay because it's inconvenient to you too? This is not a valid argument. It's also bad policy.
No, I'm not saying that. I'm pointing out that many of the developers use these systems in their "Sunday" jobs, so we know how users are affected because we are affected by the same changes.
There is an argument that comes up occasionally saying that the developers don't know what it's like in the "real world" and we cause so many problems for clerks and leaders because we don't understand what they need. Many of us use our software weekly (or more often) and we spend time alpha and beta testing on our own wards and stakes before we ever release changes to a larger beta group, let alone the entire Church.