I think a lot of people/companies are integrating workflows like that, it's just separate from the point of agent pair coding.
The interesting thing here is agents working together to be better at a single task. Not agents integrated in a workflow. There's a lot of opportunity in "if this then that" scenarios that has nothing to do with two agents communicating on one single element of a problem, it's just Agent detect -> agent solve (-> Agent review? Agent deploy? Etc.)
I used to work for a company whose primary product was a web server that companies could buy and run for use purely internally. Our pages involved a lot of data entry that could be lost, so that sort of pop-up can be handy in that situation as well.
Of course a better solution wouldve been a program which doesnt so easily let you lose data in the first place, but this software was long past that.
It's pretty cynical to call that knowledge useless. It's learning to do a thing you want to know how to do. That has use to you and often those around you. As for hard engineering problems, just because they're more complex doesn't make the knowledge less available. There's a massive amount of engineering knowledge free online, it only takes the initiative to go out and use it to learn it. The curriculum of many entire university degrees is now available for free online in a way its never been before.
For me, it popped open an email to them in outlook. Not exactly what I was expecting or what I wanted.. I couldn't figure out how to make my own graph...
We created this tool for physicians to give us feedback on the engine that drives hGraph. You can define what is considered "healthy" and rank each metric's importance in your overall health.
"Out of interest, what kind of open source solution do you envisage when you say that "DLNA will die an instant and painful death the moment a truly open solution is adopted"?
Would it involve hardware, or something installed on the TV, or something else entirely?"
Did you click the link? This is an example of a truly open solution, and it involves hardware.
Miracast isn't "open" - devices require certification, and the Miracast and Wi-Fi Direct specifications cost $200 each. It's also supported by relatively few devices right now (since, you know, certification), and I seem to recall there are some compatibility issues between manufacturer implementations.
It's not building a computer, but there was a post on here a few days ago about a group creating 'sticker circuitry', which essentially consisted of a set of stickers that you could put together to make simple circuits. Seems like a cool idea that gets down to the fundamentals while taking out the hard-to-approach, error-prone aspect.
The article is unclear about what exactly needs to be enabled in order for the app to work, but I don't think they are saying they can hijack wifi even when it's disabled. An important quote from the article on this note is
"So while PDQ doesn’t require existing connections, it uses the existing wireless chips to send data across short distances, which could be useful during power outages or natural disasters. That means you can’t have your iPhone in airplane mode while using PDQ, for example, because then it wouldn’t be able to tap into its wireless chips."
It's a stretch, but I think the implication is that even if your wifi router is out of power, two powered on phones will be able to communicate, even with "wifi" disabled as long as the wifi or bluetooth radio can get power.
Transfers even without power, as in wireless network routers/towers don't have power, but phones still do.
The short answer is there really isn't a way to prevent screenshots. Snapchat has attempted to do so, but without much success. On iOS, it detects if either of the two buttons required to take a screenshot are pressed, and hides the image right away - preventing a screenshot unless the two are pressed truly simultaneously. In my experience, this works much better than on Android, where phones have a variety of ways to screenshot, and no great method exists to stop people from taking one.
The interesting thing here is agents working together to be better at a single task. Not agents integrated in a workflow. There's a lot of opportunity in "if this then that" scenarios that has nothing to do with two agents communicating on one single element of a problem, it's just Agent detect -> agent solve (-> Agent review? Agent deploy? Etc.)
reply