4 ms·

Also, the 'clang' robots that come to mind have a certain amount of self-reliance. The 'non-clang' robots (which are basically macro's running in VMs), stop wor

Also, the 'clang' robots that come to mind have a certain amount of self-reliance. The 'non-clang' robots (which are basically macro's running in VMs), stop working as soon as an unexpected popup appears, the software is upgraded or the products on one page are suddenly on two. No, the 'non-clang' robots are an indication of the software engineers' gross failure to properly integrate and standardize data exchange between solutions.

9nGQluzmnq3M 7y ago
The article is referring to contact center (support) automation with this kind of thing, which is a pretty far cry from Selenium scripts. https://cloud.google.com/solutions/contact-center/ https://cloud.google.com/solutions/contact-center/
- edejong 7y ago
  I didn't read the article but skimmed. Guilty as charged <blush-emoji> Thought it was about RPA (Robotic Process Automation).
- marvin 7y ago
  Speaking from knowledge of the rhetoric in the Norwegian banking sector of the last few years (which is very automated), "robots" in the banking sector has referred to three things: Chatbots that don't work, macros that click around in a user interface to perform repetitive backoffice or customer support tasks, or plain old software that automates business processes in a scalable manner. Not surprisingly, only the last of these stand the test of time, and most organizations that jump on the bandwagon will realize that they need to hire more software engineers and automate their business processes at the root. For some, this is a long and painful realization. I spent six months trying to convince the appointed leader of a "robotization" initiative that what they were doing is actually software engineering, and that involving developers at an early point would be a better use of their money. They eventually made the mistake themselves, and got their own developers 18 months later. Maybe 20 years from now, we will have technologists on the board and in executive positions at these companies, and these decisions can be made in an adult manner.

9nGQluzmnq3M 7y ago

The article is referring to contact center (support) automation with this kind of thing, which is a pretty far cry from Selenium scripts. https://cloud.google.com/solutions/contact-center/ https://cloud.google.com/solutions/contact-center/

edejong 7y ago
I didn't read the article but skimmed. Guilty as charged <blush-emoji> Thought it was about RPA (Robotic Process Automation).
marvin 7y ago
Speaking from knowledge of the rhetoric in the Norwegian banking sector of the last few years (which is very automated), "robots" in the banking sector has referred to three things: Chatbots that don't work, macros that click around in a user interface to perform repetitive backoffice or customer support tasks, or plain old software that automates business processes in a scalable manner. Not surprisingly, only the last of these stand the test of time, and most organizations that jump on the bandwagon will realize that they need to hire more software engineers and automate their business processes at the root. For some, this is a long and painful realization. I spent six months trying to convince the appointed leader of a "robotization" initiative that what they were doing is actually software engineering, and that involving developers at an early point would be a better use of their money. They eventually made the mistake themselves, and got their own developers 18 months later. Maybe 20 years from now, we will have technologists on the board and in executive positions at these companies, and these decisions can be made in an adult manner.