You're most welcome. And newbie really doesn't matter in this field since everything seem to move so quickly. As far as you're working on a real life project plus stay updated to new releases. You'll be just fine.
For me point 1 hits the most. One additional problem can be on the other spectrum as well, if we create complex governance then our "quick" wins aren't that quick at all. Learning curve is something that is keeping me at night but I think this is something that all developers strugle with currently
Yeah the learning curve is a bit general of all Developers. But the view that has been marketed about RPA being a cheap Quick solution really made people treat it as a bandaid rather than a scalable long terme initiative.
The last point about vision models also called multi modals is interesting. This means the technology is already there to make most RPA jobs redundant. It is matter of time before the code is created to automatically write the RPA template through use of videos of the screen with the steps that the business users want to automate. It can track even all the videos of multiple user sessions and itself decide what to automate.
Yeah a video to process model can do the trick, but even with what we have today a good enough model can explore a website that has never seen before and do actions much like a human would based on continuous screenshots. Exciting times are ahead.
As a consultant who works on improving processes and using UiPath (and now AI) to improve business performance, I'm not as worried about being "replaced." Still, the constant churn in UiPath and AI makes interviewing for just the UiPath side of a position difficult. Answering a "How would code this" has completely changed in the last ten months, especially as it relates to document analysis. How well do I know Python? Well enough to ask ChatGPT to create a short macro and then Invoke Code, but not well enough to memorize all the detailed formatting. Does that mean that I know Python? Academically, no. Practically? Hmm. As for the points you make, I tell people that robots are happy, not-so-bright dogs that are good at following directions. It may take a while to train (program them) so you get the same outcome every time. But change the pattern (my dog prefers blue balls), and the dog gets confused. You have to keep up with the training, and the owner really needs more training than the dog. It helps - sometimes, but its often oversold.
Definitely knowing only selectors and how to create processes in UiPath doesn't seem enough in the eyes of recruiters or developers anymore. Having the AI knowledge to at least know what's going on is quite important.
Our Business process Analyst always make sure that the errors / scenarios that bot may encounter will be mentioned in the PDD itself for business Sign off before development, this acts as shield that its not developers mistake for those errors. Coming to the graph you have shown we follow the same format for iteration planning in 3 x 3 matrice effort vs Benifits. I don't think AI can't over take Uipath automations for atleast 5 years especially where something like dynamic selectors/ selector issues come. Coming to powerAutomate, I have just started with it for automations can't be done with uipath, so I kept its copliot quiet busy with all questions
Yeah protecting yourself with a good Process Design Document is necessary. As far as AI writing UiPath xaml code that we can directly use inside of studio, it's still not possible because UiPath is literally introducing and changing activities with every release, so our job is protected in that sense, but if AI is so advanced and has internet Access I will still worry about the risk.
yes when someone uses non standardized processes or even processes with REFramework with added state machines makes it harder to read and modify the workflow...
I've been doing RPA for a while and all three points hit home to me. The short lead time expectations, the zero maintenance mentality, and the always changing code landscape is crazy.
What you are saying is 100% true, I really felt working with UiPath/AA -expectation is too high whereas things are not like that and then there are a lot of issues that are actually at the first place are not the best for automation/simply worst for test automation but who can make the upper management understand.
I understand, been there and seen companies choose the worst processes to be their first robot to be implemented, but you can never convince them otherwise...
It is and they are working on different approaches either full UI Automation through visual agents or a mix of code and vision. So much to keep up with.
Humans will be needed for the computers short comings, but they wont be as in-demand as they were, meaning they will be paid much less. Being paid less will make RPA developers choose other jobs
We'll need to wait for a couple of months to see how much of a complex processes AI Models can create and then we'll know if AI only going to ease up our job significantly, replace part of it or all of it.
Whatever career you get into you have to see the extent in which AI is making easier and faster. in the case of RPA now we have AI Automation in Power automate that will allow you to create the process by recording the screen, describing in an audio or just prompting it. Same thing for UiPath, you can find an Autopilot that you can prompt to create the process you want and you can also find autopilot for so many other products they have (example UiPath apps Autopilot to create apps just from a prompt or a picture...). AI still isn't there in terms of automating a whole process, so only someone who knows how to use it will replace others, AI itself can't replace devs for the foreseeable future.
I wanted to get into RPA but I’m a complete beginner. So I’m going with python data science first l. Then if I’m fine with it take the rpa classes. Thank you for your insight. I want to choose career path that’s long lasting. So I should take a AI class also
After taking 2-3 yr of experience in rpa can we switch to software engineer ? Plz reply Becoz i have an offer of rpa developer but i wanted to get into software developer ment becoz i am much interested in coding can i able to switch after taking 2 yr of experience in rpa? And also i have good knowledge of java
![BRASIL vs. URUGUAY [1-1] | RESUMEN | ELIMINATORIAS SUDAMERICANAS | FECHA 12](http://i.ytimg.com/vi/-hWBAuxF1eY/mqdefault.jpg)
Watch how you can create a robot to generate Dalle 3 images ruclips.net/video/urtFRvSdnKw/видео.html
Great video! I’m a newbie RPA at my current employer and we’re just starting to ramp up so this is all great info!
You're most welcome. And newbie really doesn't matter in this field since everything seem to move so quickly.
As far as you're working on a real life project plus stay updated to new releases. You'll be just fine.
Hey, friend I'm also new in this field so can you please tell me the salary expectations!
For me point 1 hits the most. One additional problem can be on the other spectrum as well, if we create complex governance then our "quick" wins aren't that quick at all.
Learning curve is something that is keeping me at night but I think this is something that all developers strugle with currently
Yeah the learning curve is a bit general of all Developers.
But the view that has been marketed about RPA being a cheap Quick solution really made people treat it as a bandaid rather than a scalable long terme initiative.
The last point about vision models also called multi modals is interesting. This means the technology is already there to make most RPA jobs redundant. It is matter of time before the code is created to automatically write the RPA template through use of videos of the screen with the steps that the business users want to automate. It can track even all the videos of multiple user sessions and itself decide what to automate.
Yeah a video to process model can do the trick, but even with what we have today a good enough model can explore a website that has never seen before and do actions much like a human would based on continuous screenshots.
Exciting times are ahead.
Hey man, very happy to see an actual expert speaking of RPA and the link with new emerging tech. You definitely deserve more visibility.
As a consultant who works on improving processes and using UiPath (and now AI) to improve business performance, I'm not as worried about being "replaced." Still, the constant churn in UiPath and AI makes interviewing for just the UiPath side of a position difficult. Answering a "How would code this" has completely changed in the last ten months, especially as it relates to document analysis. How well do I know Python? Well enough to ask ChatGPT to create a short macro and then Invoke Code, but not well enough to memorize all the detailed formatting. Does that mean that I know Python? Academically, no. Practically? Hmm. As for the points you make, I tell people that robots are happy, not-so-bright dogs that are good at following directions. It may take a while to train (program them) so you get the same outcome every time. But change the pattern (my dog prefers blue balls), and the dog gets confused. You have to keep up with the training, and the owner really needs more training than the dog. It helps - sometimes, but its often oversold.
Definitely knowing only selectors and how to create processes in UiPath doesn't seem enough in the eyes of recruiters or developers anymore.
Having the AI knowledge to at least know what's going on is quite important.
Our Business process Analyst always make sure that the errors / scenarios that bot may encounter will be mentioned in the PDD itself for business Sign off before development, this acts as shield that its not developers mistake for those errors.
Coming to the graph you have shown we follow the same format for iteration planning in 3 x 3 matrice effort vs Benifits.
I don't think AI can't over take Uipath automations for atleast 5 years especially where something like dynamic selectors/ selector issues come. Coming to powerAutomate, I have just started with it for automations can't be done with uipath, so I kept its copliot quiet busy with all questions
Yeah protecting yourself with a good Process Design Document is necessary.
As far as AI writing UiPath xaml code that we can directly use inside of studio, it's still not possible because UiPath is literally introducing and changing activities with every release, so our job is protected in that sense, but if AI is so advanced and has internet Access I will still worry about the risk.
Maintenance is hell with these, trying to read others automation is also hell
yes when someone uses non standardized processes or even processes with REFramework with added state machines makes it harder to read and modify the workflow...
I've been doing RPA for a while and all three points hit home to me. The short lead time expectations, the zero maintenance mentality, and the always changing code landscape is crazy.
What you are saying is 100% true, I really felt working with UiPath/AA -expectation is too high whereas things are not like that and then there are a lot of issues that are actually at the first place are not the best for automation/simply worst for test automation but who can make the upper management understand.
I understand, been there and seen companies choose the worst processes to be their first robot to be implemented, but you can never convince them otherwise...
Very nice topic ! I'm still a bit worried about AI in this industry.
The progress is somehow really fast.
It is and they are working on different approaches either full UI Automation through visual agents or a mix of code and vision. So much to keep up with.
Humans will be needed for the computers short comings, but they wont be as in-demand as they were, meaning they will be paid much less. Being paid less will make RPA developers choose other jobs
We'll need to wait for a couple of months to see how much of a complex processes AI Models can create and then we'll know if AI only going to ease up our job significantly, replace part of it or all of it.
That should be titled "Harsh Reality of RPA Not Meeting Expectations", but still good video. Thank you 😁
Thank you so much for the videa, I would love to transition to RPA as i'm a software engineer. What are the steps I can take
Follow me on LinkedIn I make more RPA Content on there, I will also make a video about this topic.
So what would be a career to get into that AI wouldn’t dominate or not for long which covers most things needed to work in IT
Whatever career you get into you have to see the extent in which AI is making easier and faster.
in the case of RPA now we have AI Automation in Power automate that will allow you to create the process by recording the screen, describing in an audio or just prompting it. Same thing for UiPath, you can find an Autopilot that you can prompt to create the process you want and you can also find autopilot for so many other products they have (example UiPath apps Autopilot to create apps just from a prompt or a picture...).
AI still isn't there in terms of automating a whole process, so only someone who knows how to use it will replace others, AI itself can't replace devs for the foreseeable future.
I wanted to get into RPA but I’m a complete beginner. So I’m going with python data science first l. Then if I’m fine with it take the rpa classes. Thank you for your insight. I want to choose career path that’s long lasting. So I should take a AI class also
🌟🌟🌟
After taking 2-3 yr of experience in rpa can we switch to software engineer ? Plz reply
Becoz i have an offer of rpa developer but i wanted to get into software developer ment becoz i am much interested in coding can i able to switch after taking 2 yr of experience in rpa?
And also i have good knowledge of java
With UiPath, you can also use C# to modify or enhance the process. You can make the transition to Software developer while working on RPA
Jackson Paul Williams Jason Harris Edward
Wilson Margaret Brown Jeffrey Robinson Gary
Thomas Larry Hall Sarah Wilson Donna
Davis Eric Anderson Christopher Harris Brian