11

Fiddling with the UiPath RPA tool. What the fuck is this monster?

So, you create apps by drawing a flowchart, like some kid using Scratch. Then, suddenly, you have to create a .NET object just to get a random number!

Who the fuck is the target audience that can create objects, call a directory read function, etc, but can't write a loop?! Show me that fucking person.

Then I have to debug the fucking selectors when they don't work correct. All this requires is understanding how UIs are structured under the hood. So, you know that a menu bar is a window, but you need to draw a fucking if statement?!

And how would you debug and manage this monstrosity?

It like we learned nothing from all the Excel apps we build for decades.

I mean, it's an impressive app. But, why does it exist?

Someone needs to stop this before it gets out into the wild or we'll all be debugging flowchart a created by business analysts.

You have been warned. Join the fight or accept the consequences.

Comments
  • 2
    @rutee07 Fortunately, that kind of tech stays in the dev world. We can strangle it at birth.

    This RPA thing is pitched at C-suite and enterprise. If it gets in, we are utterly fucked.

    Not because we'll have no work. We'll actually have *more* work as it'll take forever to fix stuff. But, it'll be soul destroying work.

    And, building flowcharts as a sprint will then be an actual thing. I mean...just think about that. Read it again. Building flowcharts in a sprint. That'll be dev in 2021.

    I'm preparing for a career change already.
Add Comment