4 ms·
On one hand, having the fresh eyes of an objective third party review code feels like a great idea. What I'm stuck on is mostly the legal implications. 1) Do
by chiefalchemist 9y ago
On one hand, having the fresh eyes of an objective third party review code feels like a great idea.
What I'm stuck on is mostly the legal implications.
1) Do companies want a relatively unknown poking around in their secret sauce? Ages ago, my father worked on a number of projects at Bell Labs where parts for custom prototypes where sourced to different vendors so none knew exactly what was being built. Yes, now is not then. None the less how will this risk be mitigated (beyond contracts and background checks)?
2) And what if something does go wrong? The reviewer(s) miss something and eventually the shit hits the fan. Now what?
No show stoppers. But friction enough to be curious how they fare.
- paulie_a 9y agoYour secret sauce is your sales team and ability to get customers to use the features. Outside of dropping secret keys etc, your actual implementation in source code is nearly irrelevant. If you depend on keeping your code a total secret you are in for a world of hurt. Ex-employees certainly have copies laying around that could be leaked intentionally or just nabbed by some malware
- fizwhiz 9y agoyou do realize that trade secrets are a thing, right?
- hyperpallium 9y agojust not in enterprise code
- agitator 9y agoThat's an odd position to take.... If there was nothing special about the code you worked on, then the product is probably not all that significant. I mean, why work on something if there is no technology differentiating you?
- paulie_a 9y ago> i mean, why work on something if there is no technology differentiating you? Technology doesn't differentiate, value propositions do.