It's a pretty egregious failure for the org because it controlled the conditions for it to happen.
replyThe security guy is just the patsy because he actioned it.
They have obviously done this a million times before and now they got burned.
Yes, this. That same engineer shouldn’t have a pocket nuclear trigger shaped just like their key fob, either. Humans are predictable.
replyPretty much the definition of a “career limiting event”
replyIt's either a a Career Limiting Event, or a Career Learning event.
replyIn the case of a Learning event, you keep your job, and take the time to make the environment more resilient to this kind of issue.
In the case of a Limiting event, you lose your job, and get hired somewhere else for significantly better pay, and make the new environment more resilient to this kind of issue.
Hopefully the Wikimedia foundation is the former.
In the average real world, the staff engineer learns nothing, regardless of whether they get to lose or keep their job. Some time down the line, they make other careless mistakes. Eventually they retire, having learned nothing.
replyThis is more common than you'd think.
They'll be fine, recruiters don't look this stuff up and generally background checks only care about illegal shit.
replyNobody is going to know who did this, so probably not career limiting in any major way.
replyThey named him in the support ticket linked here somewhere.
reply> sbassett
[flagged]
replyIs ok, the AI was going to replace them in a few weeks anyway.
reply