The NSA is tasked with collecting intelligence from foreign sources as well as securing US government information systems from attack. As the private entities listed are components of our nation's critical infrastructure, keeping them secure is probably a good idea. I wouldn't wait for Siemens and its ilk to step up to this task.
Its probably not a perfect separation of government, private industry, domestic and foreign intelligence tasks. But since the NSA has the expertise, I say let them help out. Its not like operating utilities and other infrastructure companies isn't already subject to extra regulation and oversight. Its just a shame the SEC/CFTC doesn't keep as close an eye on our banks.
Take a look at the Lego Technic line. Lots of axles, wheels, gears, levers, motors, pneumatics, etc. They integrate pretty well with the traditional block sets as well. And then one can step up to the Mindstorms line of programmable controllers, actuators and sensors.
Insist on a one person reporting structure. The moment you are reporting to more that one person all is lost as each then is competing for your time and will try to shove in more features or reporting demand than the other.
This is a good point. Have all of the consultants' requests for info. go through your program manager. It will keep demands on your time channeled through him/her and give the PM visibility of your work load. The more consultant crap you get, the further the primary project will slide.
If that doesn't work, you can always game the system. When one consultant asks you to do something, you can always claim to be working on something for another. Let them fight it out. But that might be burning bridges, so have an exit strategy figured out.
This is why polygamy works so well. Each wife thinks you are with another one. So you can sneak off to the shop and get some work done.
If you tap the energy of tornadoes to generate power, it will reduce their remaining energy. Tap enough energy and they might become nearly extinct. If this happens, mobile homes, with no remaining natural predators, will multiply out of control.
Management gave us (Engineering) a task to complete. Either do it by hand or automate it. They didn't care. Just get it done right, on time and for a reasonable budget.
The code started to get shitty when the computing group found us writing our own tools and took the task away. The code stank, but it was blamed on poorly defined requirements (which they collected). The s/w folks didn't have any responsibility for actually performing our work and missing schedule was our problem, not theirs. As long as we waited patiently in line for their change process, they didn't get dinged for delays. And to top it all off, when they took over our apps (NLP of engineering requirements documents to produce executable code), they just started pulling claims of NP-hard out of their backsides as to why they were getting into trouble. We (Engineering) would never have dreamed of lobbying management for the responsibility for a task and then turned around and claimed we didn't understand how to do it.
If it were possible to split a crystal and communicate between two entangled halves (assume no FTL, causality violations, etc.), the technology would be classified and locked up immediately. No government, particularly our own, would tolerate the existence of a communications system that operated over an uninterceptable medium.
In the event of a 'real life situation' involving your own self defense, missing three times is quite possible. In some cases one or two (poorly placed) hits won't stop an attacker.
That whole 'shoot them once and they go down' is pure Hollywood stuff.
OK, use solar sails. Augment the thrust with heat emitted by RTGs, reversing the effect that is decellerating Pioneer. Make it a big heat source and design a round trip robotic* mission to survey the system.
*Robotic because we don't want it returning with a bunch of Reavers from the unshielded core.
I don't know about that. You can place "No Trespassing" signs around your property and then have an interloper charged with that crime. Its not like these signs produce some sort of force field that one must attack to overcome. They signify the intent to keep the property (or for uid/passwords; data) secured.
Of course, you should use a good password. But if some third party tries to guess it, that signals their intent to obtain unauthorized access.
Slashdot Mirror
Same reason you weight yourself in stone when you are on a diet. It makes the numbers sound better.
Call me when Greenland is warm enough to support agriculture.
The NSA is tasked with collecting intelligence from foreign sources as well as securing US government information systems from attack. As the private entities listed are components of our nation's critical infrastructure, keeping them secure is probably a good idea. I wouldn't wait for Siemens and its ilk to step up to this task.
Its probably not a perfect separation of government, private industry, domestic and foreign intelligence tasks. But since the NSA has the expertise, I say let them help out. Its not like operating utilities and other infrastructure companies isn't already subject to extra regulation and oversight. Its just a shame the SEC/CFTC doesn't keep as close an eye on our banks.
Take a look at the Lego Technic line. Lots of axles, wheels, gears, levers, motors, pneumatics, etc. They integrate pretty well with the traditional block sets as well. And then one can step up to the Mindstorms line of programmable controllers, actuators and sensors.
Looks pretty flat to me.
Meanwhile, in related news, North Korea is conducting large scale human tests by feeding segments of their their population nothing but skinny mice.
Insist on a one person reporting structure. The moment you are reporting to more that one person all is lost as each then is competing for your time and will try to shove in more features or reporting demand than the other.
This is a good point. Have all of the consultants' requests for info. go through your program manager. It will keep demands on your time channeled through him/her and give the PM visibility of your work load. The more consultant crap you get, the further the primary project will slide.
If that doesn't work, you can always game the system. When one consultant asks you to do something, you can always claim to be working on something for another. Let them fight it out. But that might be burning bridges, so have an exit strategy figured out.
This is why polygamy works so well. Each wife thinks you are with another one. So you can sneak off to the shop and get some work done.
If you tap the energy of tornadoes to generate power, it will reduce their remaining energy. Tap enough energy and they might become nearly extinct. If this happens, mobile homes, with no remaining natural predators, will multiply out of control.
Management gave us (Engineering) a task to complete. Either do it by hand or automate it. They didn't care. Just get it done right, on time and for a reasonable budget.
The code started to get shitty when the computing group found us writing our own tools and took the task away. The code stank, but it was blamed on poorly defined requirements (which they collected). The s/w folks didn't have any responsibility for actually performing our work and missing schedule was our problem, not theirs. As long as we waited patiently in line for their change process, they didn't get dinged for delays. And to top it all off, when they took over our apps (NLP of engineering requirements documents to produce executable code), they just started pulling claims of NP-hard out of their backsides as to why they were getting into trouble. We (Engineering) would never have dreamed of lobbying management for the responsibility for a task and then turned around and claimed we didn't understand how to do it.
An entertaining analysis. It will get people to sit and watch it rather than reading some dry paper on the topic and forgetting it in a few hours.
You couldn't have posted this a bit sooner than the day before December 21, 2012?
If it were possible to split a crystal and communicate between two entangled halves (assume no FTL, causality violations, etc.), the technology would be classified and locked up immediately. No government, particularly our own, would tolerate the existence of a communications system that operated over an uninterceptable medium.
http://www.youtube.com/watch?v=KvLoUNlwNBM
In the event of a 'real life situation' involving your own self defense, missing three times is quite possible. In some cases one or two (poorly placed) hits won't stop an attacker.
That whole 'shoot them once and they go down' is pure Hollywood stuff.
So then its a lot like the RIAA.
OK, use solar sails. Augment the thrust with heat emitted by RTGs, reversing the effect that is decellerating Pioneer. Make it a big heat source and design a round trip robotic* mission to survey the system.
*Robotic because we don't want it returning with a bunch of Reavers from the unshielded core.
I don't know about that. You can place "No Trespassing" signs around your property and then have an interloper charged with that crime. Its not like these signs produce some sort of force field that one must attack to overcome. They signify the intent to keep the property (or for uid/passwords; data) secured.
Of course, you should use a good password. But if some third party tries to guess it, that signals their intent to obtain unauthorized access.
IANAL.
Aren't there any equivalent US laws? Or is no one in US interested in prosecuting?
Not if one doesn't want to put themselves on the shit list of our shadow government.
manager, n; Bringer of doom. See: PHB.
Where I used to work, using the verb "manage" was a sign of impending doom.
Dell will just rename it Kwangmyongsong.