Within a couple of years, 50 percent of the organizations that had planned to replace their customer service personnel with AI models are expected to reverse their...
I use it almost every day, and most of those days, it says something incorrect. That’s okay for my purposes because I can plainly see that it’s incorrect. I’m using it as an assistant, and I’m the one who is deciding whether to take its not-always-reliable advice.
I would HARDLY contemplate turning it loose to handle things unsupervised. It just isn’t that good, or even close.
These CEOs and others who are trying to replace CSRs are caught up in the hype from Eric Schmidt and others who proclaim “no programmers in 4 months” and similar. Well, he said that about 2 months ago and, yeah, nah. Nah.
If that day comes, it won’t be soon, and it’ll take many, many small, hard-won advancements. As they say, there is no free lunch in AI.
I gave chatgpt a burl writing a batch file, the stupid thing was putting REM on the same line as active code and then not understanding why it didn’t work
It is important to understand that most of the job of software development is not making the code work. That’s the easy part.
There are two hard parts::
-Making code that is easy to understand, modify as necessary, and repair when problems are found.
-Interpreting what customers are asking for. Customers usually don’t have the vocabulary and knowledge of the inside of a program that they would need to have to articulate exactly what they want.
In order for AI to replace programmers, customers will have to start accurately describing what they want the software to do, and AI will have to start making code that is easy for humans to read and modify.
This means that good programmers’ jobs are generally safe from AI, and probably will be for a long time. Bad programmers and people who are around just to fill in boilerplates are probably not going to stick around, but the people who actually have skill in those tougher parts will be AOK.
A good systems analyst can effectively translate user requirements into accurate statements, does not need to be a programmer. Good systems analysts are generally more adept in asking clarifying questions, challenging assumptions and sussing out needs. Good programmers will still be needed but their time is wasted gathering requirements.
Systems analyst is like a programmer analyst without the coding. I agree, in my experience small shops were more likely to have just programmer analysts. Often also responsible for hardware as well.
If it’s just you I hope you didn’t need a systems analyst to gather requirements and then work with the programmer to implement them. If you did, might need another kind of analysis. ;)
I use it almost every day, and most of those days, it says something incorrect. That’s okay for my purposes because I can plainly see that it’s incorrect. I’m using it as an assistant, and I’m the one who is deciding whether to take its not-always-reliable advice.
I would HARDLY contemplate turning it loose to handle things unsupervised. It just isn’t that good, or even close.
These CEOs and others who are trying to replace CSRs are caught up in the hype from Eric Schmidt and others who proclaim “no programmers in 4 months” and similar. Well, he said that about 2 months ago and, yeah, nah. Nah.
If that day comes, it won’t be soon, and it’ll take many, many small, hard-won advancements. As they say, there is no free lunch in AI.
I gave chatgpt a burl writing a batch file, the stupid thing was putting REM on the same line as active code and then not understanding why it didn’t work
And a lot of burnt carbon to get there :(
Have you ever played a 3D game
It is important to understand that most of the job of software development is not making the code work. That’s the easy part.
There are two hard parts::
-Making code that is easy to understand, modify as necessary, and repair when problems are found.
-Interpreting what customers are asking for. Customers usually don’t have the vocabulary and knowledge of the inside of a program that they would need to have to articulate exactly what they want.
In order for AI to replace programmers, customers will have to start accurately describing what they want the software to do, and AI will have to start making code that is easy for humans to read and modify.
This means that good programmers’ jobs are generally safe from AI, and probably will be for a long time. Bad programmers and people who are around just to fill in boilerplates are probably not going to stick around, but the people who actually have skill in those tougher parts will be AOK.
A good systems analyst can effectively translate user requirements into accurate statements, does not need to be a programmer. Good systems analysts are generally more adept in asking clarifying questions, challenging assumptions and sussing out needs. Good programmers will still be needed but their time is wasted gathering requirements.
Most places don’t have all good system analysts.
True.
For this to make sense AI has to replace product-oriented roles too. Some C-level person says “make products go brrrrrr” and it does everything
What is a systems analyst?
I never worked in a big enough software team to have any distinction other than “works on code” and “does sales work”.
The field I was in was all small places that were very specialized in what they worked on.
When I ran my own company, it was just me. I did everything that the company needed to take are of.
Systems analyst is like a programmer analyst without the coding. I agree, in my experience small shops were more likely to have just programmer analysts. Often also responsible for hardware as well.
If it’s just you I hope you didn’t need a systems analyst to gather requirements and then work with the programmer to implement them. If you did, might need another kind of analysis. ;)