Re:Elon Musk emails employees about 'extensive and damaging ...
by davidgay on Tuesday June 19, 2018 @12:31AM
(#17343853)
Then the system that allowed them to do so is badly designed.
[ Parent
| on HN ]
Re:Elon Musk emails employees about 'extensive and damaging ...
by chillee on Tuesday June 19, 2018 @12:53AM
(#17343955)
At Facebook, you could alter code even after somebody had given the OK for code review. I know some people specifically kept some small commits open after being approved, just so they could quickly make changes without needing approval if they ever needed to.
Re:Elon Musk emails employees about 'extensive and damaging ...
by skj on Tuesday June 19, 2018 @07:52AM
(#17345711)
At Google you can mark something as TBR (to be reviewed), as long as you're one of the designated owners for that code.
Re:Elon Musk emails employees about 'extensive and damaging ...
by sneak on Tuesday June 19, 2018 @06:11AM
(#17345223)
“Dear respected members of Congress, ...”
Re:Elon Musk emails employees about 'extensive and damaging ...
by noobermin on Tuesday June 19, 2018 @12:41AM
(#17343892)
I guess my thinking is if the disgruntled employee was so upset over not getting a promotion to cause so much damage they must have been in a high enough position already to warrant such a disposition, and "high enough" might mean high enough to have push access themselves.
Edit: see closeparens comment above. Complicated systems can always be subverted when trust is broken.