Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "blue prism"
You write a list of instructions. The machine reads this list and runs your commands.
Quite similar to procedural programming but you group your functions via objects.
Learned of this new paradigm quite recently working with Blue Prism, which is essentially the program doing whatever it wants from crashing, freezing, returning wrong results, sometimes working properly, with no reason whatsoever other than the sheer malice of those beasts of burden who designed it in the first place. Mark my words, BP devs, you will be held accountable for your crimes against God and humanity.6
9 months ago my boss promised I would not be working on RPA anymore.
Monday, at 12:00, my boss assigned to me the maintenance of 13 robots.
Monday, at 15:00, I was talking to a recruiter and discussing my next job.
We all make Blue Prism the receving end of our jokes and that's actually very unfair, they even developed their own sorting algorithms, fuckYouSort, and that's something I want to acknowledge.2
> Blue Prism just stopped working
And that's how 12 time-critical processes in production just went out of the window for no fucking reason other than the sheer malice of those beasts of burden who designed BP in the first place :)
0 days since last catastrophic blue prism crash6
Want to hear another joke?
Blue Prism allows you to export stuff from version 6.7 to 6.3.
However they changed 𝘷𝘦𝘦𝘦𝘦𝘳𝘺 slightly the way they store the position of the nodes. No new features -or at least nothing that you would care about- but the structure of the node itself want went from
<position x=1 y=2 w=3 h=4></position>
The whole project collapsed to a single point, catastrophic consequences as far as exception handling. A generic "fuck you" for no real reason other than the sheer malice of those beasts of burden who developed Blue Prism in the first place.
And I have two different versions of Blue Prism on dev and prod :)2
Making some changes to a Blue Prism process I have never seen before
Q: Can we test these changes before going live?
A: No. We are going to pinpoint the problems on the road
Q: Nasty. However we can retry the process if anything goes wrong
A: No. It runs 5:00 to 17:00
Q: Wait, so I have one shot at making this shit work and it's tomorrow?
Yesterday at 2:00 I noticed 2 of the 3 machines are dead, now the process is self destructing every 5 minutes and my mentor, who usually spend weeks without answering phone calls, apparently learned again how do smartphones work 'cause this time he did fucking call.2
A CASE AGAINST BLUE PRISM
Let's review one of the worst weeks I had with Blue Prism
Monday: Yay! Solved one of the problems we've been carrying around for a week before.
One of the robots suddenly became slow. Like, REAL slow. A process that would take 3 minutes per record now takes 45, and that broke apart all the following schedule.
There were no updates on the application server, the production machine, the robot, it just became slow. And not always slow; a process manually run from console room would work, a process in debug room would work, it's just the scheduled part that caused problems.
It turned out, BP didn't seem to like that particular combination of schedulation + process + machine. Moving the process to a different machine seemingly fixed that. IDK why.
Tuesday: One of our processes waits for a code to appear in the page, and when that happens, it memorizes this code. However, now it is always returning blank. Worked for months, now it breaks every single time.
After half a day of debugging a bug which DIDN'T HAPPEN IN DEBUG MODE YET AGAIN, at 11pm I decided to just place a nonsensical timeout in page before reading and call it a day.
WEDNESDAY: a scheduled process didn't start. "No sessions created". Thanks Blue Prism, very cool.
THURSTAY: This time, schedulation did start, but the process is "waiting". As in: it's 9:30 am, the process has been stuck in the same step since 6:00 am. Turns out, it blocked during a navigate stage; you need to send a string to clipboard using the standard BP action for that, then paste and click "enter", but for some reason the standard BP object sent "ORRCO" instead of "ORRICO" to clipboard, which obviously returned no results and then... the process just didn't feel like doing things anymore. No errors, no logs, nothing: just sitting on its ass. Because fuck you that's why.
Friday: another process uses a very moderate amount of scripts to work. Nothing really fancy, just a couple of lines of code to place in page some IDs and selector to help BP do its thing, otherwise selecting these elements would be a nightmare.
The same script -it's not dynamically generated-worked yesterday, the day before and the day after. But sometimes it will not. Why? The answer, my friend, is blowin'' in the wind
First day of new job. No more rants about Blue Prism, that's in the past now. New year new me!
Time to go back to rant against backend developers and their fucking Laravel.
First lesson of the day: if I see another select2 I'm gonna commit war crimes. You see this nice plugin for jQuery, you use it everything's so cool and modern and you think you're the smart one of the team 'cause you don't know you've just polluted an otherwise perfectly fine web page with the dirtiest js shit you could possibly find, just because you didn't feel like searching one more minute for whatever replacement for a drop down you can easily find.
You're not the smart one. You're a criminal.4
I'm working again with blue prism on a very very old SAP website. A hundred thousand nested iframes with a hundred thousand nested tables.
Please kill me, I long for the sweet embrace of death5
> Mister IHateForALiving, we have an automated procedure which downloads files from a website. You should update it and use the new webservice instead.
Sounds cool, just send me the documentation
> Oh yeah, have this example of a request
... Dude, this thing has 10 parameters. None of them are named, and 7 of them are actually nulled. How do I fill this thing?
Oh, ehm... Let's ask the client then!
> NONONONO, we told the client this update was live at least 3 months ago, we can't begin asking questions now
Ouch. How much time do I have to make sense of this mess?
> The new supplier should take charge by the end of the month, I'd like this to be live by Tuesday
Needless to say, it's not going well, but that ain't none of my business1