I don't think that dpritchett was talking about open source vs closed source work. He was talking more about NDA-covered work, which could be on open or closed source code.
For most of the "normal" closed source work, it's easy to say that you worked on X product or feature, and can talk about some of the challenges that you encountered with it.
Contrast that with defense contract work that requires classified clearance. If you're a developer on that, you will most likely never be able to talk about it to most recruiters or interviewers before you retire. There is no way to actually talk about what you've done with the general public. That can hurt a career, especially if it puts a black hole in your experience on a resume.
Ah, I didn't pick that up from the thread. Fair enough; I agree, if you can't even talk about what you're working on in a future job interview, you should price that into your comp.
It may close off an outside career, but it also opens it up within the huge company that you are doing the secret work for.
I don't know of any reqs within my company (GlobalDefenseCorp) that indicate salary is increased when you go dark. Your compensation is that you get to work on cool shit, which will likely lead to another project in the same vein.
For most of the "normal" closed source work, it's easy to say that you worked on X product or feature, and can talk about some of the challenges that you encountered with it.
Contrast that with defense contract work that requires classified clearance. If you're a developer on that, you will most likely never be able to talk about it to most recruiters or interviewers before you retire. There is no way to actually talk about what you've done with the general public. That can hurt a career, especially if it puts a black hole in your experience on a resume.