2,000 karma · joined December 3, 2011
The Little Engine That Could and The Grapes of Wrath are good and all...
Has anybody read any of the others?
Example... oh, there's lots of people with TS clearances in this little town in the midwest. Maybe there's something to that. Let's check it out.
If possible, avoid this by teaming with a center that already has these certifications.
Title: Computer Engineer
Years Exp: 12
Next Move: Open up a bookstore with my wife. Hope to open later this year. With luck, it will be successful enough that I can take a stab at starting a software business.
If neither of those apply then you probably have nothing to worry about.
By the way, not all info security jobs require a TS. A lot of government/contractor jobs, even in the infosec field, just require a secret clearance. Same questions, same form, but the bar is lower.
In the middle of the meeting, she blurts out, "Fuck this. I don't need this shit."
She gets up, leaves the meeting, and walks back to her desk. She drops her stuff in a box, walks out of the building, and drops her base pass off at the main gate.
Nobody heard from her again.
Another route you can take, depending on the agencies you are selling to, is to sell it to existing federal contractors. There is usually a "materials" line in their contract for buying stuff to bypass the normal process. This is common with DOD, not sure about others.
Good luck.
"out-sourcing the slow/painful bits"
Which is exactly why I don't get the obsession with side projects or work samples. There is no guarantee that the person showing the work actually did the work. At best, it means they have access to people that can do the work, which I suppose is something.
Not that I am accusing you of cheating or lying or anything, just pointing out that in a world where outsourcing is easy and common that you can't take these things at face value.
And problem sets need to be updated or they will feel dated very quickly. Especially if you are supposed to be using technology to help solve the problem.
But I went to the site a couple of times and "I love turtles." was the most coherent message I received.
Take that as you will.
If that's the case you can word the NDA so that it gives them what they want and you don't give up anything you don't want to give up.
It could also be that in order to implement the game (or whatever) you could require access to business strategy information (like pricing, upgrade dates...) that they want to keep secret. You can word the NDA to cover this but not the technical stuff.
Or if none of this applies then you can point out that NDAs don't cover information that is available publicly so any "ideas" typically won't be covered once they are publicly available.
And as others have pointed out always have your own template to start from.
Ada struck me as a language that would be a pain to write in(at least it would take a long time) but it was a pleasure to read. Even without an intimate knowledge of the language (I was a C++ guy) I was able to figure it out.