News for hackers. Stuff that matters.

A comment on GitLab Database Incident – Live Report. Parent comment

Re:GitLab Database Incident – Live Report by avar on Wednesday February 01, 2017 @07:43AM (#13540246)
That guy is going to be interviewing at some company with someone who's obsessive enough about outage reports to remember a then-obscure one years later, but enough of an idiot to not understand that people aren't personally to blame for this sort of stuff?

Sounds like even in that very contrived scenario the guy involved would dodge a bullet in not being hired by a bunch of idiots.

[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by nsxwolf on Wednesday February 01, 2017 @11:02AM (#13541711)
"I worked at GitLab."

Googles name + GitLab, finds postmortem

Highly likely, and now you don't get to tell your own story and emphasize what you want to.

[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by woof on Wednesday February 01, 2017 @12:32PM (#13542810)
Awsome postmortem -is there any thing you would do differently today?

What's your most valuable lesson from that incident?

You're hired!

[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by drvdevd on Wednesday February 01, 2017 @12:11PM (#13542551)
also, maybe some people on here are perfect, but if you've used Unix for more than half your life (as I have) you've 'rm -rf'-ed some stuff.

I think people who've been through disasters have a much better understanding of the importance and methods of not ending up there than those with a perfectly clean record.

IOW, I'd hire the "rm -rf" guy first if he owns it.

[ Parent | on HN ]