20 years ago at a trade show, a new module based visual coding tool was introduced in my field which claimed “You’ll never need another programmer”.
Oddly enough, I still have a job.
The tools have gotten better, but I still write code every day because procedural programming is still the best way to do things.
It is just now reaching the point that we can do some small to medium scale projects with plug and play systems, but only with very specific equipment and configurations.
The pace of change is about every five years, and some elements are always in transition.
All in one turn key solutions are always one to two cycles behind, so may work great with the stuff I’m already replacing.
I think these are honest attempts to simplify, but by the time they have it sorted its obsolete. If I have to build modules anyway to work with new equipemnt, might as well just write all the code in my native language.
These also tend to be attempts at all in one devices, requiring you to use devices only compatible with those subsystems. I want to be able to use best tech from what ever manufacturer. New and fancy almost always means a command line interface, which again means coding.
20 years ago at a trade show, a new module based visual coding tool was introduced in my field which claimed “You’ll never need another programmer”.
Oddly enough, I still have a job.
The tools have gotten better, but I still write code every day because procedural programming is still the best way to do things.
It is just now reaching the point that we can do some small to medium scale projects with plug and play systems, but only with very specific equipment and configurations.
20 years ago while learning web development Dreamweaver was going to supposedly eliminate the need for code on websites too. lol
But sadly, the dream of eliminating us seems like it will never die
It’s because people trying to sell silver bullets is nothing new.
The pace of change is about every five years, and some elements are always in transition.
All in one turn key solutions are always one to two cycles behind, so may work great with the stuff I’m already replacing.
I think these are honest attempts to simplify, but by the time they have it sorted its obsolete. If I have to build modules anyway to work with new equipemnt, might as well just write all the code in my native language.
These also tend to be attempts at all in one devices, requiring you to use devices only compatible with those subsystems. I want to be able to use best tech from what ever manufacturer. New and fancy almost always means a command line interface, which again means coding.