Here's what you're getting wrong, I think: "we are not far away from machine outperforming humans in every way".
AI can perform coding task better than humans, already, but humans know what to ask for and how to apply that result. That's what critical thinking is.
In conclusion, developers won't lose their jobs to AI. They'll lose their jobs to other developers using AI.
So if you don't want to lose your job, learn how to use AI and how to test the output, as you'll do a lot of it pretty soon, if you don't already.
From my POV, what is more troublesome is an AI who learns how to learn and therefore think. When that happens, our disadvantage will be being humans, not being developers. And it's illogical to think it won't happen, IMHO.
To be clear: I thought your article was a very interesting intellectual exercise. You yourself are clearly intelligent and thoughtful. I think where you missed was implying that Dragos’ article was somehow negative or fear-driven compared to your own. In actuality, there was little comparison to be made between the two articles, yours being a theoretical discussion and Dragos’ being a practical suggestion for present times.
Peter is the former President of the New Zealand Open Source Society. He is currently working on Business Workflow Automation, and is the core maintainer for Gravity Workflow a GPL workflow engine.
I've been working on AI since I was a boy of 11. I played with very simple Eliza and wrote my own text networks, which were perhaps an early GPT (not really). Learn about AI by all means. Remember when Covid hit there was the 'learn to code' meme, which only reinforced that not everyone can code, or frankly would want to. ML and AI technology isn't as easy. I mean you can use PyTorch to train and use a model, or just use OpenAI API, but that's like driving a car vs building one. So plenty of coders will be left behind.
Me, being the monster I am, is currently building a No Code platform. The core technology is already written, and has been in use for ten years, but now I'm working on getting it ready for release as a SaaS solution.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Here's what you're getting wrong, I think: "we are not far away from machine outperforming humans in every way".
AI can perform coding task better than humans, already, but humans know what to ask for and how to apply that result. That's what critical thinking is.
In conclusion, developers won't lose their jobs to AI. They'll lose their jobs to other developers using AI.
So if you don't want to lose your job, learn how to use AI and how to test the output, as you'll do a lot of it pretty soon, if you don't already.
From my POV, what is more troublesome is an AI who learns how to learn and therefore think. When that happens, our disadvantage will be being humans, not being developers. And it's illogical to think it won't happen, IMHO.
To be clear: I thought your article was a very interesting intellectual exercise. You yourself are clearly intelligent and thoughtful. I think where you missed was implying that Dragos’ article was somehow negative or fear-driven compared to your own. In actuality, there was little comparison to be made between the two articles, yours being a theoretical discussion and Dragos’ being a practical suggestion for present times.
My web site is:
devcentre.nz/#/
I've been working on AI since I was a boy of 11. I played with very simple Eliza and wrote my own text networks, which were perhaps an early GPT (not really). Learn about AI by all means. Remember when Covid hit there was the 'learn to code' meme, which only reinforced that not everyone can code, or frankly would want to. ML and AI technology isn't as easy. I mean you can use PyTorch to train and use a model, or just use OpenAI API, but that's like driving a car vs building one. So plenty of coders will be left behind.
Me, being the monster I am, is currently building a No Code platform. The core technology is already written, and has been in use for ten years, but now I'm working on getting it ready for release as a SaaS solution.