4 ms·
Fortune 500 company, Junior dev. Tried to log into our staging database, which has the same username, but different password than production. Tried 3 times, go
by Posibyte 9y ago
Fortune 500 company, Junior dev. Tried to log into our staging database, which has the same username, but different password than production.
Tried 3 times, got the locked out error. Got frustrated, said I'd fix it after lunch, went out to eat, came back about 3 hours later after a doctor's appointment.
My boss was waiting for me at the department door and I got sent back to his office for a stern talking to. I had locked out the production user from the database, causing every app in the company to go offline. I was then told to read aloud back all of the projected sales losses from that day as well as write a bunch of letters for our top sales people who couldn't make sales that day.
Wasn't fired (thankfully). Made it to a senior lead, so if I had to say anything, it's that the punishment really made it really drive home and I _never ever did it again_ . :)
- nieksand 9y agoI have a hard time seeing how this was your fault. It seems like a poorly designed system is the root cause, not you.
- loco5niner 9y agoI agree with nieksand... badly designed system. It's better for companies to recognize these design flaws and fix them, rather than blame employees ignorant actions.
- planteen 9y agoDid you have different credentials you were supposed to be using?
- colanderman 9y agoWhat a sadistic and irresponsible boss.
- verdex_phone 9y agoI dont know. Ive seen systems before where anyone could make catastrophic 'modifications' like what you describe. I tend towards blaming the system construction over the junior developer.