Low Code or RPA? (again)

Regular readers of my weekly newsletter will recognise that this is a topic I've discussed before. On our first outing, I concluded that both RPA and Low Code had its own place in a complementary way: Low-Code: Collaborator or Challenger for the RPA Crown?

Last week, I was speaking at a UK Mendix Event (Mendix on Tour) on the topic of Delivering Results with the AI Ecosystem. I enjoy discussing both principles and practice, and on this occasion, I was fortunate enough to share the stage with Simon Black, Mendix Guru, Evangelist and a kid in a candy shop when it comes to the opportunities afforded by the AI ecosystem. While I explained the principles, Simon demonstrated the practice live for everyone to see for themselves.

We both realised that there is still a lot of confusion about the different roles RPA and Low Code have to play, questions at the end focused more on this than on the opportunity provided by AI! As I have concluded before, they are different but complementary, but today I have a helpful summary of those differences and when you might select one over the other:

unnamed (1).png

Coincidentally, analysts Horses for Sources recently cited research which identified that the most significant barrier to change is an insufficient understanding of disruptive changes (blog link here). As we saw during Mendix on Tour, Businesses are simply unaware of the art of the possible. It's difficult to advance when there is a lack of education on the opportunities that technology can provide.

On this theme, we are just one week away from our webinar with Richard Hill and Gina Gray from Celaton; an Intelligent Process Automation solution that provides a one-stop shop for combining RPA and machine learning capabilities. Sign Up for the Webinar on 16th July here.

For anyone looking to advance their Blue Prism Skills, our next online instructor-led training begins on 16th July, sign up here for just $349. For corporate arrangements, contact be@therpaacademy.com for details.

Thanks Everyone.


Can we kill the word “developer”? How prepared are you for your knowledge journey?

Career Journey.jpeg

Can we really kill the word “developer”?

I just think it is too narrow a definition.

When I hear the word “Developer”, I get the feeling that:

  • You are not interested in the operation side

  • Cyber security is not on your radar.

  • Networks - meh! They are someone else’s problem.

  • Scalability - well, kind of my thing.

  • Project management - not me

  • Compliance - there’s a department for that….

Of course, that is total bull$#!t.

You are highly engaged in these areas.

For a small part, because you’d be negligent not to be. But mainly because this is your career and this is all exciting stuff. And it is only going to get more exciting and faster. And that will translate in to real money.

Over the coming months you’ll see us doing a number of things to help you with your skills as a “technologist”, not a developer. Many of these things go way beyond technology and in to skills and capabilities for your life as a whole.

Currently we live in a siloed world.

The project paths, knowledge paths and career paths have huge barbed wire fences around them. The structural world does not believe that that someone in RPA needs to learn anything about IoT or Data Science.

In reality, the rapid adoption of “digital" will be killed by any barriers at all to knowledge.

But back in 2019, these barriers exist, big time.

More on this in the coming weeks, and some big announcements by the end of summer.

For you to access real success, you need to know that this requires you going way wider than “knowledge”.

It requires you to be prepared for your knowledge journey.

More specifically, your long term knowledge journey, the application of that knowledge, plus the sharing of what you’ve learned.

So, this week’s Question Of The Week is about how prepared you are for your knowledge journey.