3 ms·

> ...I really don’t give a shit and say just give the government everything and it’s weird to see people try to throw up layers... Yeah, this always struck me

> ...I really don’t give a shit and say just give the government everything and it’s weird to see people try to throw up layers... Yeah, this always struck me as so strange. I worked at a contractor where our customer really did own all of the deliverables, but I had peers who worked at contractors where that wasn't the case. To them, I was all like, "Guys. Our tax money is paying for this. Why are you rooting for pulling money out of everyone's pocket to massively enrich a few fat cats and sales guys in your company?". Like, if you're of a "We're not going to give everything to the government" persuasion, then the reasonable way to handle that is to give the government the deliverables to do anything they want with, just so long as you're free to sell the unclassified components of it (and things derived from them) in the private sector to interested parties without interference.

scottyah 2y ago
I've seen it where development happens under one Customer, then a few years later they get some bad management and flounder, then a new Customer team (or teams) has pretty much the same mission. It's nice to be able to carry what you've already done with you vs starting over. The Defense Sector is very much like the private sector in that it has hundreds of companies/teams doing pretty much the same thing.
- simoncion 2y ago
  Oh yeah. Starting from something fairly-reasonable is far, far better than starting from scratch . And yeah, I used to do defense work. For the most part, it's exactly like non-defense work, with one of the big differentiators being that to work from home, you'd often need to build a SCIF in your home. (Good fucking luck with getting that approved.)