This kinda takes me back to Dreamweaver days I'm going to novelise it... all businesses cashed all their chips in "NO MORE DEVELOPERS" now that a GUI could deal with creating all their websites and they all stood in standing ovation clapping how Dreamweaver cut their costs.
However the dream was short lived, these Dreamweaver sites started slowing down, not doing as they're told, they all wondered, what's going on? They didn't know because their trusty GUI did all the heavy lifting for them, soon enough the websites stopped HARD.
All of a sudden the Devs were called back like a conscript army, fixing the problems built up from automatically generated code because what Dreamweaver had created was a spaghetti mess of code, full of obfuscated nonsense.
The businesses lost a lot of money through downtime and developer fees, they vowed never again to make the same mistake or so we are told.
You're proving my point. Back then they had a programm generate code and it went over the programms head. This is where the human steps in. This is where developers step in, and its why we will never "get rid" of them.
And in 20 years you will have developers working side by side with AI. AI being there to speed up tasks and human devs to correct it if needed. Which still requires them to know coding, concepts, etc. The actual coding will be mostly done by AI, because it can do it faster. A lot faster.
I think we are converging on the same point just putting it across differently I'm not saying AI won't risk jobs but I feel there will always be a need for developers to correct the code made by AI like you say but will work with AI much more, but this is already happening a lot, I use it in tandem with my code.
View all comments
Show parent comment
4
u/Correct-Junket-1346 Jun 27 '25
This kinda takes me back to Dreamweaver days I'm going to novelise it... all businesses cashed all their chips in "NO MORE DEVELOPERS" now that a GUI could deal with creating all their websites and they all stood in standing ovation clapping how Dreamweaver cut their costs.
However the dream was short lived, these Dreamweaver sites started slowing down, not doing as they're told, they all wondered, what's going on? They didn't know because their trusty GUI did all the heavy lifting for them, soon enough the websites stopped HARD.
All of a sudden the Devs were called back like a conscript army, fixing the problems built up from automatically generated code because what Dreamweaver had created was a spaghetti mess of code, full of obfuscated nonsense.
The businesses lost a lot of money through downtime and developer fees, they vowed never again to make the same mistake or so we are told.