This had a huge mindshare for me when deciding who to approach as a co-founder. While I'm younger and incredibly healthy, my ideal co-founder is 9 years older than me and spent much of his 20s as a semi-professional athlete. It's catching up to him now. After I approached him, I brought up healthcare and that I knew it would be important to him and that we'd figure that out together somehow. We were both disappointed at how little healthcare reform shelters entrepreneurs. In the end, languishing at someone else's company, but insured, is not the way he wanted to spend his life. If he had a family, that might have been a harder decision to make.
It's worth pointing out that you don't need to work "for the NSA" to be contributing to state surveillance. If someone is hired straight out of college to work for any type of cloud services provider with revenues over a billion, it's probably safe to say that they your prospective employer has enough market reach to have attracted the attention of state surveillance programs. Of course, by law, your prospective employer would be required to lie to you about involvement.
> It's worth pointing out that you don't need to work "for the NSA" to be contributing to state surveillance.
The flip is also true: you're not necessarily contributing to state surveillance just because you work "for the NSA". Two easy examples are SELinux and the various NSA Guides to Securing <OS_of_choice>.
