The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
T | *
a | *
s | *
k | *
s | *
A developer (or team) has a lot of tasks to complete, but most of them are quite easy.
There are some difficult tasks, but they are few. (Your mileage may vary.)
Tools such as described, and ETL packages and such, address only the easiest tasks.
But developers don't need help with those, we need help with the difficult tasks.
Whenever a vendor announces, "we have a tool which will solve all your problems", you can be assured that it actually addresses only the "low-hanging fruit" -- and no one needs help with "low-hanging fruit", that's the definition of "low-hanging fruit"!
At best, such systems can allow a team to expend less time/energy on easy tasks and concentrate on the difficult ones.
And/or allow an enterprise to hire low-paid contractors to deal with the "low-hanging fruit" in a way that the "real" developers can understand and support once the contractors have left.
And if it ever gets to do it... we will probably have other bigger problems to worry about
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Based on the responses so far, developers clearly underestimate the power of low code. I am not familiar with the Microsoft one but I am familiar with Mendix and it is powerful enough to run businesses. It can do anything .Net can do and much easier to build.
Those that think this is just a passing fad will be passed by this "fad."
Microsoft was offering "no code database development" in Visual Basic 3, and that was released in 1993.
It's true, using VB3 you could build a database system by doing nothing more than dragging and dropping controls onto a form and clicking the property showing where you'd like to source the data from.
Yet here we are, 27 years later, and I'm continuing to have a good career as a software developer specializing in databases.
No code systems will continue to exist, they will continue be used by "Power users" who all have varying degree of skill, and they will continue to be the bane of the real IT professional who is asked to come up and fix the mistakes of the "Power user", usually after data is lost or a business critical limitation is reached.
Why invent two access operators "." and "->", when you could just use "*pf.x" and be more consistent? Or use "->" to dereference all pointers?
I get the feeling bits of the C spec were thrown in just before the submission deadline ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!