3 ms·
I'm trying to imagine the architecture that led to this.
by sillysaurus3 8y ago
I'm trying to imagine the architecture that led to this.
- dsnuh 8y agoTrust me, I couldn't imagine it either. My guess is it actually probably broke on the second John Smith that joined, and they had to manually configure all subsequent John Smiths, and they just wait until they get a ticket.
- elcritch 8y agoAlternatively a dev thinks gotta handle user name collisions: "try creating user... hmmm if exists append ‘1’ and repeat with 2..n+1, oh uhhh, better stop after, idk, 5 times (last time my test borked and filled up the database with username ‘(null)’ last time, sigh)". Programmer takes lunch.
- fooker 8y agoA plain fixed size C array embedded in some data structure somewhere? Doesn't seem that big a stretch to imagine.
- dsnuh 8y agoThis would be more like Windows batch jobs or Powershell scripts. I honestly think it just cannot handle duplicate names at all, and they wait until they get a complaint. When we were acquired, we had a person on our team receieiving emails for a different user with the same name that previously existed in the company that acquired us.