Years ago in my computer sciences classes, the prof would draw part of a system on one side of the chalkboard connected into one side of a blob with another part of the system connected out the other side. He/she would go on and on about the input parameters and presentation protocols, blah, blah and more blah. But if you asked what went on in the middle, represented by the blob, you'd be told something like "This course is EE2xx. That part is in another course, EE3xx. You are welcome to sign up for it next semester. But we don't have time to cover it right now."
Fast forward 30 years and that blob is referred to as "the cloud." and in fact, the blob drawn in class often had a cloud shaped appearance. People think of "the cloud" as some marvelous place where miracles happen. But the reality is that "the cloud" is often just another system controlled by someone else and they are responsible for what happens inside. So "the cloud" is often a nifty way to push off responsibility, cost (and blame for when it blows up and critical data goes into the bit bucket) onto someone else.
You think the NFRTR is messed up now? Just wait until ATF puts it into "the cloud" and has a contractor to blame for the mess!
Vanderwerf still on the payroll?
ReplyDeleteYears ago in my computer sciences classes, the prof would draw part of a system on one side of the chalkboard connected into one side of a blob with another part of the system connected out the other side. He/she would go on and on about the input parameters and presentation protocols, blah, blah and more blah. But if you asked what went on in the middle, represented by the blob, you'd be told something like "This course is EE2xx. That part is in another course, EE3xx. You are welcome to sign up for it next semester. But we don't have time to cover it right now."
ReplyDeleteFast forward 30 years and that blob is referred to as "the cloud." and in fact, the blob drawn in class often had a cloud shaped appearance. People think of "the cloud" as some marvelous place where miracles happen. But the reality is that "the cloud" is often just another system controlled by someone else and they are responsible for what happens inside. So "the cloud" is often a nifty way to push off responsibility, cost (and blame for when it blows up and critical data goes into the bit bucket) onto someone else.
You think the NFRTR is messed up now? Just wait until ATF puts it into "the cloud" and has a contractor to blame for the mess!