3 ms·
Another former employee here. When our company was acquired, all of the engineers were given these guidelines immediately (signing/agreeing was a non-negotiabl
by xmcredpol 11y ago
Another former employee here.
When our company was acquired, all of the engineers were given these guidelines immediately (signing/agreeing was a non-negotiable precondition of keeping your job).
It was essentially a blanket ban on any programming outside of work. No open source contributions, game development, or work on any software used in current (or future!) Amazon markets. The language was such that even learning (courses, books, writing a single line of test code, etc) was a prohibited.
Some of this was surely just liability reduction gone mad, but the totality of it felt like a tool to limit the career options of employees. Some kind of Kafkaesque talent retention strategy.
- Terretta 11y agoNo. An analysis of contribution patterns would signal to GCE, Azure, etc., what they're up to, in advance. Not a good strategy.