The way I see it, there are two types of developers we should take into consideration for this discussion:
Software Engineers
Code editors
Most “programmers” these days are really just code editors, they know how to search stack overflow for some useful pointers, copy that code and edit it to what they need. That is absolutely fine, this advances programming in so many ways. But the software engineers are the people that actually answer the stack overflow questions with detailed answers. These engineers have a more advanced skillset in problem solving for specific coding frameworks and languages.
When people say: programmers are cooked, I keep thinking that they mean code editors, not software engineers. Which is a similar trend in basically all industries in relation with AI. Yes, AI has the potential to make some jobs in health care obsolete (e.g. radiologist), but that doesn’t mean we no longer need surgeons or domain expert doctors. Same thing applies to programming.
So if you are a developer today, ask yourself the following: Do actually know my stuff well, am I an expert? If the answer is no, and you’re basically a code editor (which again, is fine), then you should seriously consider what AI means for your job.
I agree with the overall sentiment, but I’d like to add two points:
Everyone starts off as a code editor, and through a combination of (self-)education and experience can become a software engineer.
To the point of code editors having to worry about LLM’s taking their job, I agree, but I don’t think it will be as over the top as people literally being replaced by “AI agents”. Rather I think it will be a combination of code editors becoming more productive through use of LLMs, decreasing the demand for code editors, and lay people (i.e. almost no code skills) being able to do more through LLMs applied in the right places, like some website builders are doing now.
If the “code editor” uses AI they will never become a software engineer.
“Oh I will just learn by asking AI to explain” that’s not happening. You won’t learn how to come.up with a solution. Mathematiciams know better than anyone you can’t just memorize how the professor does stuff and call yourself a problem solver. Now go learn the heruistic method.
As much as people hate it, stackoverflow people rarely give the answer directly. They usually tell you easier alternative methods or how to solve a similar problem with explanation.
They way it will work is that every single college student that relies on AI and gets away with “academic dishonesty, the tool” will become terrible programmers that can’t think for themselves or read a single paragraph of documentation. Similar consequences for inexperienced developers.
The way I see it, there are two types of developers we should take into consideration for this discussion:
Most “programmers” these days are really just code editors, they know how to search stack overflow for some useful pointers, copy that code and edit it to what they need. That is absolutely fine, this advances programming in so many ways. But the software engineers are the people that actually answer the stack overflow questions with detailed answers. These engineers have a more advanced skillset in problem solving for specific coding frameworks and languages.
When people say: programmers are cooked, I keep thinking that they mean code editors, not software engineers. Which is a similar trend in basically all industries in relation with AI. Yes, AI has the potential to make some jobs in health care obsolete (e.g. radiologist), but that doesn’t mean we no longer need surgeons or domain expert doctors. Same thing applies to programming.
So if you are a developer today, ask yourself the following: Do actually know my stuff well, am I an expert? If the answer is no, and you’re basically a code editor (which again, is fine), then you should seriously consider what AI means for your job.
I agree with the overall sentiment, but I’d like to add two points:
Everyone starts off as a code editor, and through a combination of (self-)education and experience can become a software engineer.
To the point of code editors having to worry about LLM’s taking their job, I agree, but I don’t think it will be as over the top as people literally being replaced by “AI agents”. Rather I think it will be a combination of code editors becoming more productive through use of LLMs, decreasing the demand for code editors, and lay people (i.e. almost no code skills) being able to do more through LLMs applied in the right places, like some website builders are doing now.
If the “code editor” uses AI they will never become a software engineer.
“Oh I will just learn by asking AI to explain” that’s not happening. You won’t learn how to come.up with a solution. Mathematiciams know better than anyone you can’t just memorize how the professor does stuff and call yourself a problem solver. Now go learn the heruistic method.
As much as people hate it, stackoverflow people rarely give the answer directly. They usually tell you easier alternative methods or how to solve a similar problem with explanation.
They way it will work is that every single college student that relies on AI and gets away with “academic dishonesty, the tool” will become terrible programmers that can’t think for themselves or read a single paragraph of documentation. Similar consequences for inexperienced developers.