I did mention in my article that big companies will push the pedal on this movement, because it will allow them to save time and money.
And most Low Code / No Code tools are affordable.
As for internal tools, it depends.
Internal tools usually have a terrible ROI (Return On Investment).
And you rarely see innovative companies building an internal tool, when there is an affordable commercial alternative.
For example, I've never heard of a company building their own internal video calling solution, even if they can do it with open source technologies such as WebRTC.
They all just prefer to use Zoom or Google Meet.
And I've never heard of an innovative company trying to build their own Email Software, they just use Microsoft Outlook.
This is also how Endtest is a game changer, companies no longer need to build their own internal overcomplicated Selenium framework.
I get a feeling you don't have much experience as a developer. Typically internal tooling isn't something that is budgeted and replacing other tasks, it's something that happens alongside main duties.
Zoom, GMeet and Outlook aren't app builder or business automation applications. In enterprise settings those tools in the Microsoft offering are quite popular, which I assume is the reason you don't mention those.
Typically Selenium is used together with tooling that records user behaviour and/or generates configuration automatically based on some data source. Could you elaborate on why you think this is "overcomplicated"?
I do have lots of experience writing code:
JavaScript, React, PHP, Python, Shell Scripts, Apple Scripts and a bit of Java.
I'd say my favourite one is Python.
But our discussion shouldn't be about what I think vs. what you think.
In the article, I'm mostly presenting the facts and the direction in which the market is moving, based on research from independent sources.
If you had news articles like this:
UIPath is closing down, because no company wants to do low-code automation
Airtable is not expanding, because companies don't want to build apps with their platform
I would have said that your opinion is correct.
If you have any data or valid resources to back up your claims, that would make the discussion more interesting.
You'd like me to explain why using Selenium leads to overcomplications?
I did mention in my article that big companies will push the pedal on this movement, because it will allow them to save time and money.
And most Low Code / No Code tools are affordable.
As for internal tools, it depends.
Internal tools usually have a terrible ROI (Return On Investment).
And you rarely see innovative companies building an internal tool, when there is an affordable commercial alternative.
For example, I've never heard of a company building their own internal video calling solution, even if they can do it with open source technologies such as WebRTC.
They all just prefer to use Zoom or Google Meet.
And I've never heard of an innovative company trying to build their own Email Software, they just use Microsoft Outlook.
This is also how Endtest is a game changer, companies no longer need to build their own internal overcomplicated Selenium framework.
I get a feeling you don't have much experience as a developer. Typically internal tooling isn't something that is budgeted and replacing other tasks, it's something that happens alongside main duties.
Zoom, GMeet and Outlook aren't app builder or business automation applications. In enterprise settings those tools in the Microsoft offering are quite popular, which I assume is the reason you don't mention those.
Typically Selenium is used together with tooling that records user behaviour and/or generates configuration automatically based on some data source. Could you elaborate on why you think this is "overcomplicated"?
Your assumption is incorrect.
I do have lots of experience writing code:
JavaScript, React, PHP, Python, Shell Scripts, Apple Scripts and a bit of Java.
I'd say my favourite one is Python.
But our discussion shouldn't be about what I think vs. what you think.
In the article, I'm mostly presenting the facts and the direction in which the market is moving, based on research from independent sources.
If you had news articles like this:
UIPath is closing down, because no company wants to do low-code automation
Airtable is not expanding, because companies don't want to build apps with their platform
I would have said that your opinion is correct.
If you have any data or valid resources to back up your claims, that would make the discussion more interesting.
You'd like me to explain why using Selenium leads to overcomplications?
I actually made a video about that last year:
youtube.com/watch?v=uJSC_YwXYZw
Junior developers worry about syntax and languages, experienced developers worry about data structures.
I'd appreciate if you linked a transcript instead.