News for hackers. Stuff that matters.
Re:Reflecting on one very, very strange year at Uber by brudgers on Sunday February 19, 2017 @10:12PM (#13683964)
HR already investigated. Putting the Chief Human Resource Officer in charge implies what the investigation will conclude: rouge employees. Because if it was institutional, the CHRO would be responsible.

Then again, it isn't a commitment to cleaning out HR beyond anyone there who says, 'Oh I think it is ok.' And the whole 'thinking' thing is a way of backing off under the cover of 'We don't want to be thought police.'

There's no taking of responsibility for what happened on his watch. No personal commitment to action. No promise of full disclosure. This is damage control and the fact that HR is in charge of investigating allegations against it suggests that the plan is cover up. The CEO sets the culture.

Re:Reflecting on one very, very strange year at Uber by tarr11 on Sunday February 19, 2017 @10:31PM (#13684051)
Looks like the CHRO was hired in November.
Re:Reflecting on one very, very strange year at Uber by brudgers on Sunday February 19, 2017 @10:54PM (#13684159)
If the investigation was serious, chief council or the CEO would be doing it. The new hire provides more cover for the rouge employees conclusion by providing a plausible 'it did not happen on my watch'. C-level positions hit the ground running and the sort of events described in the article are bread and butter regardless of industry. After three months there's no way this was a blind side.
Re:Reflecting on one very, very strange year at Uber by skj on Sunday February 19, 2017 @11:35PM (#13684319)
Only because you did it twice...

"rogue".

Re:Reflecting on one very, very strange year at Uber by brudgers on Monday February 20, 2017 @03:20PM (#13690539)
I shall add it to my cannon of mistakes.