4 ms·

obviously you should read the contract before signing with $MEGACORP_THAT_PAYS_YOUR_BILLS, and I agree with (1) and (2) and (3) kinda sorta not really since it

obviously you should read the contract before signing with $MEGACORP_THAT_PAYS_YOUR_BILLS, and I agree with (1) and (2) and (3) kinda sorta not really since it basically just implies you are a work machine, but it just seems so rife with the potential for abuse. Thankfully I haven't heard of many other cases of this getting people in too much trouble other than Serge Aleynikov and his case with GS (and honestly, it was stupid of him to upload even open source code from work computer to a remote server). I worked at GS and it was the most locked down development environment ever, so it wouldn't even be feasible/productive for you to "accidentally" work on side projects on these machines. Most security/audit trainings were around "Really - if you do this, you will instantly be teleported into the center of the nearest neutron star"

yongjik 5y ago
> Serge Aleynikov IIRC, he saw some open source code used in Goldman Sachs, believed that they should be open (whether right or wrong, I don't know), and uploaded it public. Right? I remember HN discussion from years ago. I don't think his story is related to developers' side projects. If you work for Company X and knowingly upload some of its internal repository to a public place, of course you're going to be fired. Would you expect anything else?
- arthurcolle 5y ago
  from my understanding it was more nuanced than that - the code was already open source but he then made some changes to the source and wanted to keep those changes. Obviously this is pretty bad too, but eventually all charges were dropped and this might have just been because how aggressive the plaintiffs and the FBI goons were in pursuing this guy, especially after considering the accusations of "stealing code" that is so dangerous it could manipulate the fabric of financial markets. In any case, I just pulled up my GS NDA and I probably shouldn't comment any further. Funny side note though: GS realtime risk/lazily loaded object graph database is called SecDB, and @saleyn has a repo on GitHub called secdb which has to do with having an efficient data store for financial data... I guess he was feeling invulnerable after getting off of the previous charges haha

yongjik 5y ago

> Serge Aleynikov IIRC, he saw some open source code used in Goldman Sachs, believed that they should be open (whether right or wrong, I don't know), and uploaded it public. Right? I remember HN discussion from years ago. I don't think his story is related to developers' side projects. If you work for Company X and knowingly upload some of its internal repository to a public place, of course you're going to be fired. Would you expect anything else?

arthurcolle 5y ago
from my understanding it was more nuanced than that - the code was already open source but he then made some changes to the source and wanted to keep those changes. Obviously this is pretty bad too, but eventually all charges were dropped and this might have just been because how aggressive the plaintiffs and the FBI goons were in pursuing this guy, especially after considering the accusations of "stealing code" that is so dangerous it could manipulate the fabric of financial markets. In any case, I just pulled up my GS NDA and I probably shouldn't comment any further. Funny side note though: GS realtime risk/lazily loaded object graph database is called SecDB, and @saleyn has a repo on GitHub called secdb which has to do with having an efficient data store for financial data... I guess he was feeling invulnerable after getting off of the previous charges haha