3 ms·

Pretty much everyone takes a copy of the codebase they've been working on with them when they leave, unless it's too huge to copy without being noticed. For ref

Pretty much everyone takes a copy of the codebase they've been working on with them when they leave, unless it's too huge to copy without being noticed. For reference purposes more than anything. I know people with private copies of some decent chunks of FAANG source code, for example. They'd never leak it, it's tucked away just in case they want to refer back to it, for whatever reason. Just don't worry about it, it's not a big deal.

mmcallister 4y ago
This has never, not once crossed my mind. I've worked at two FAANG companies and I'm fairly certain that at least at Google they'd be able to tell you've exfiltrated some code, and even if they couldn't it's morally questionable to be doing that in the first place. High risk, very low reward
- pcthrowaway 4y ago
  I haven't worked at a FAANG but I don't delete my local copies of codebases that I largely wrote myself. Yes, it's probably illegal and ethically questionable. I don't show or sell the codebase to anyone else. It's more for me to refer to when I encounter a similar problem that I recognize I already tackled years ago. I'm not going to copy verbatim, but if it can save me time to refer to a working implementation of a solution I need to repeat, I'm going to do it. And this happens pretty rarely, but I'm competing in this job market with people who are doing the same, or, if they're not, probably have much better memories than myself. If I can keep up with competition by referencing things, it improves my own ability to do the work I do. I'm in my late 30s btw, so already at the point in my life where I need to do whatever I can to keep a competitive edge against 20-somethings in the industry... I'm very concerned about my memory continuing to get worse and the implications it may have on my employability, despite not having much money saved up. If we're ever in some weird sci-fi future where people who leave jobs have their memories erased, I'll gladly delete my copies of code I wrote. That way, at least my age will only work against me in the context of my current job. Until then, I don't see why someone with perfect recall should be able to refer to things they worked on in the past, and I shouldn't.
  - UncleMeat 4y ago
    That’s one of the tricks at google. There are no local copies. Your laptop never actually has the repo checked out into the file system.
  - airbreather 4y ago
    "I'm in my late 30s btw, so already at the point in my life where I need to do whatever I can to keep a competitive edge against 20-somethings in the industry" I am interested to explore this recurring theme, in that how does 10 years difference at that age make such a big difference? When you think a world class sprinter is not regarded to coming into their own until their 30's at best, it can't be physical condition. Then you think, is it mental condition, the ability to absorb and adapt to new things, and sharpness of memory? But I wonder if not, when I think back to my 20's and of my friends and collegues, any sharpness was well overwhelmed in a wholistic sense by inexperience and often excessive hubris. I would have said 30's is about when an individual may have accumulated enough balance and skills to really start considering to eb able to deliver, unless being managed exceptionally well earlier in life. So that leaves possible other factors 1) Many manegers are quite young these days and don't like to manage people older than them, for a wide variety of reasons. 2) Tech is cashing in on a bunch of unpaid work when they acquire fresh young talent who have worked hard in their own time for many years previous, to be up to date with the latest languagse/stacks etc. After ten years unless they have really kept up, they are stale. 3) Once you hit 30, you might be a little sick of living to work and want to spend more spare time with family and friends, so therefore maybe not doing the extra (unpaid) work to do more and/or keep up. 4) Once you hit 30, tried your guts out, been unlucky with hitting the fuck off money and still really need to work, maybe the hunger is gone. (or that is the perception) 5) It's a cult and there is no reason, but once the club has formed that's how it runs. By now I am getting more and more out there, but all of the above have some premise of plausability, but I am interested to know what everyone's experiences/thoughts are from SV/tech. Note of Context: I work in another country, in a tech based field being industrial engineering of electrical and control systems, but any ageisim doesn't seem to really kick in until after 50, if at all. But it is a bit more conservative, and uptake of new tech is much slower compared to SV because the risks are far more tangible (long lead very big money projects, possible harm to human life) and the conservative position is to do what is known to work. Breaking things is not in the normal acceptable range of outcomes. The slower rate of new tech adoption is especially because Final Investment Decision (FID) may not occur until 10-20% of potential budget has been expended doing front end studies and tightly defining the path forward to completion.
JonChesterfield 4y ago
Definitely not everyone. Referring back to stolen code would be high risk and minimal return. Instant dismissal with chance of lawsuit style risk. I periodically have to reimplement things from scratch and that is indeed irritating. Fortunately version N is usually better than N-1. The solution to that annoyance is open source.
DIVx0 4y ago
I've had about a dozen different jobs over my career and not once have I even thought about squirreling away an employers code base. I'd say this is a far from common practice. I think it would be a big deal (worth worrying about) to have physical/digital proprietary information in your possession after you left the company.
amf12 4y ago
This is an outlier rather than a norm.

mmcallister 4y ago

This has never, not once crossed my mind. I've worked at two FAANG companies and I'm fairly certain that at least at Google they'd be able to tell you've exfiltrated some code, and even if they couldn't it's morally questionable to be doing that in the first place. High risk, very low reward

pcthrowaway 4y ago
I haven't worked at a FAANG but I don't delete my local copies of codebases that I largely wrote myself. Yes, it's probably illegal and ethically questionable. I don't show or sell the codebase to anyone else. It's more for me to refer to when I encounter a similar problem that I recognize I already tackled years ago. I'm not going to copy verbatim, but if it can save me time to refer to a working implementation of a solution I need to repeat, I'm going to do it. And this happens pretty rarely, but I'm competing in this job market with people who are doing the same, or, if they're not, probably have much better memories than myself. If I can keep up with competition by referencing things, it improves my own ability to do the work I do. I'm in my late 30s btw, so already at the point in my life where I need to do whatever I can to keep a competitive edge against 20-somethings in the industry... I'm very concerned about my memory continuing to get worse and the implications it may have on my employability, despite not having much money saved up. If we're ever in some weird sci-fi future where people who leave jobs have their memories erased, I'll gladly delete my copies of code I wrote. That way, at least my age will only work against me in the context of my current job. Until then, I don't see why someone with perfect recall should be able to refer to things they worked on in the past, and I shouldn't.
- UncleMeat 4y ago
  That’s one of the tricks at google. There are no local copies. Your laptop never actually has the repo checked out into the file system.
- airbreather 4y ago
  "I'm in my late 30s btw, so already at the point in my life where I need to do whatever I can to keep a competitive edge against 20-somethings in the industry" I am interested to explore this recurring theme, in that how does 10 years difference at that age make such a big difference? When you think a world class sprinter is not regarded to coming into their own until their 30's at best, it can't be physical condition. Then you think, is it mental condition, the ability to absorb and adapt to new things, and sharpness of memory? But I wonder if not, when I think back to my 20's and of my friends and collegues, any sharpness was well overwhelmed in a wholistic sense by inexperience and often excessive hubris. I would have said 30's is about when an individual may have accumulated enough balance and skills to really start considering to eb able to deliver, unless being managed exceptionally well earlier in life. So that leaves possible other factors 1) Many manegers are quite young these days and don't like to manage people older than them, for a wide variety of reasons. 2) Tech is cashing in on a bunch of unpaid work when they acquire fresh young talent who have worked hard in their own time for many years previous, to be up to date with the latest languagse/stacks etc. After ten years unless they have really kept up, they are stale. 3) Once you hit 30, you might be a little sick of living to work and want to spend more spare time with family and friends, so therefore maybe not doing the extra (unpaid) work to do more and/or keep up. 4) Once you hit 30, tried your guts out, been unlucky with hitting the fuck off money and still really need to work, maybe the hunger is gone. (or that is the perception) 5) It's a cult and there is no reason, but once the club has formed that's how it runs. By now I am getting more and more out there, but all of the above have some premise of plausability, but I am interested to know what everyone's experiences/thoughts are from SV/tech. Note of Context: I work in another country, in a tech based field being industrial engineering of electrical and control systems, but any ageisim doesn't seem to really kick in until after 50, if at all. But it is a bit more conservative, and uptake of new tech is much slower compared to SV because the risks are far more tangible (long lead very big money projects, possible harm to human life) and the conservative position is to do what is known to work. Breaking things is not in the normal acceptable range of outcomes. The slower rate of new tech adoption is especially because Final Investment Decision (FID) may not occur until 10-20% of potential budget has been expended doing front end studies and tightly defining the path forward to completion.

JonChesterfield 4y ago

Definitely not everyone. Referring back to stolen code would be high risk and minimal return. Instant dismissal with chance of lawsuit style risk. I periodically have to reimplement things from scratch and that is indeed irritating. Fortunately version N is usually better than N-1. The solution to that annoyance is open source.

DIVx0 4y ago

I've had about a dozen different jobs over my career and not once have I even thought about squirreling away an employers code base. I'd say this is a far from common practice. I think it would be a big deal (worth worrying about) to have physical/digital proprietary information in your possession after you left the company.

amf12 4y ago

This is an outlier rather than a norm.