4 ms·
Breach of contract possibly. Usually companies don't want you revealing their internal infrastructure publicly unless you get permission. Who knows though.
by encryptluks2 4y ago
Breach of contract possibly. Usually companies don't want you revealing their internal infrastructure publicly unless you get permission. Who knows though.
- emodendroket 4y agoWouldn't that be a civil claim and not actually a law being broken then?
- wankle 4y agoThere are entire sections of the law around trade secrets (intellectual capital).
- emodendroket 4y agoNothing here seems to approach anything like truly proprietary knowledge and the kind of information it contains is pretty similar to what goes up on engineering blogs (or what you'd describe in a job interview, if you prefer) all the time.
- wankle 4y agoYes exactly this. Maybe they did but I didn't find it stated in the writeup, which was actually pretty good. If it were my company though, I'd want the intellectual capital protected and we programmers usually have to sign non-compete agreements so I think my original comment stands, it was my opinion and initial gut reaction, not an indictment or judgement in any way.
- whatshisface 4y agoYeah, now that I know that Twitter uses caches and has automatic failover I'll be able to put them out of business by competing with them. :P
- nigamanth 4y agoWho's going to compete with Twitter? It's a company worth billions, and to execute the caches and automatic fallover in the rival company with billions of users it would take billions.
- encryptluks2 4y agoTo be hair Musk posted much more internal information in a screenshot lately. The question isn't really is it incredibly useful, but is there anything that might be a breach of the employment agreements. To this I don't know, but it is still an area where employees should be careful. I personally would never write anything about my employer on a personal blog.