Doesn't have to be on the internet.
If they are on any network, and anyone brings any machine that has been connected to a network that a compromised machine has been connected to... and so on
Those laptops'll kill ya every time
It all boils down to how good the information you are getting, and how good your training is.
There's not enough information in TFA to determine how much work the agents are actually doing... whether they are making decisions on their own, or simply hiliting and collating what appears to be relevant information.
If one of the humans has to collect information from several sources and collate it, what does it hurt for the computer to do that, and include a recommendation... enough training and the recommendations just become another datapoint which you intuitively incorprate into your actions.
However, if information is hidden or removed from the human, or the agent is making decisions at too high a level, then I'm very worried.
I have re-built several helpdesk and incident response systems, and the the main productivity enhancer I bring to the table is having the server perform some basic analysis of whatever is about to be displayed.
Do basic classes, drop out for 5-10 years, then come back.
It's an entirely different experience.
Classes I know I would have skimmed through actually kept my interest, and I began to see connections that would never have sunk in.
You ever use semaphores to synchronize events across frames on a web-site?
You need to track sessions bidirectionally? There are alot of lessons learned in TCP/IPs history.
Need to prove the scalability of your design? betcha those good ol' O notations are coming in handy...
Why does Ethernet get wonky after a certain distance? no, I mean really, why? Good things to know if you are seeling your services.
Any training is as useful as you can make it, whereever you can make it.
Slashdot Mirror
Doesn't have to be on the internet. If they are on any network, and anyone brings any machine that has been connected to a network that a compromised machine has been connected to... and so on Those laptops'll kill ya every time
It all boils down to how good the information you are getting, and how good your training is.
There's not enough information in TFA to determine how much work the agents are actually doing... whether they are making decisions on their own, or simply hiliting and collating what appears to be relevant information.
If one of the humans has to collect information from several sources and collate it, what does it hurt for the computer to do that, and include a recommendation... enough training and the recommendations just become another datapoint which you intuitively incorprate into your actions.
However, if information is hidden or removed from the human, or the agent is making decisions at too high a level, then I'm very worried.
I have re-built several helpdesk and incident response systems, and the the main productivity enhancer I bring to the table is having the server perform some basic analysis of whatever is about to be displayed.
Do basic classes, drop out for 5-10 years, then come back. It's an entirely different experience. Classes I know I would have skimmed through actually kept my interest, and I began to see connections that would never have sunk in. You ever use semaphores to synchronize events across frames on a web-site? You need to track sessions bidirectionally? There are alot of lessons learned in TCP/IPs history. Need to prove the scalability of your design? betcha those good ol' O notations are coming in handy... Why does Ethernet get wonky after a certain distance? no, I mean really, why? Good things to know if you are seeling your services. Any training is as useful as you can make it, whereever you can make it.