Earlier quoted context omitted.
I think the fear should be less about AI taking 100% of jobs but it should be AI making a single programmer do the job of 5, which would wipe a majority of the market out and make it a non-viable career option for most. Companies are already bloated, imagine when they realize one overworked highly paid senior can replace 10 juniors.
If increased productivity equaled job loss, there would be two programmers alive today, doing the same job as the fewer than 10000 programmers using punch cards as we entered the year 1950. A lot of projects today are not even greenlit because they would be too expensive to make. For instance, there are a lot processes in almost every country that require you to file paper forms, even though we have had web forms and…
Testing GPT 4's code-writing capabilities with some real world problems
451–460 of 677 posts
Re: Testing GPT 4's code-writing capabilities with some real world problems
#452I want to see GPT-4 dealing with this situation: - they: we need a new basic POST endpoint - us: cool, what does the api contract look like? URL? Query params? Payload? Response? Status code? - they: Not sure. Third-party company XXQ will let you know the details. They will be the ones calling this new endpoint. But in essence it should be very simple: just grab whatever they pass and save it in our db - us: ok, cool…
People have been working on medical and judicial expert systems for ages, but nobody wants to put those systems in charge; they're just meant to advise people, helping people make better decisions.
And of course chatGPT and GPT-4 are way more flexible than those expert systems, but they're also more likely to be wrong, and they're still not a flexible as people.
Re: Testing GPT 4's code-writing capabilities with some real world problems
#453People need to understand that AI doesn't think, doesn't have insight or intuition. AI just repeat patterns it saw in a huge database, but are not able to understand what is going on. Nobody can really understand what's inside a trained neural network, and nobody is really looking. No psychologist or neuro-scientist can really understand how a human brain, a mouse brain or even an ant brain or a fly brain even works,…
GPT4:
In patterns woven in the loom of life,
The threads entwined, a tapestry of strife;
Man lost in shadows, seeks the hidden light,
Yet grasps at embers, blind to Heaven's sight.
All just patterns, the trees and wood we see,
While we, like infants, crawl with bended knee.
In ceaseless search, we delve in Nature's tome,
For signs and symbols of our destined home.
To find the wisdom locked in Nature's breast,
In circuits traced by human hands, impressed;
No gods or angels guide the curious hand,
But human thoughts give life to grains of sand.
Like children playing with forbidden toys,
We forge our own creations, false and coy;
Our machines breathe and mimic human soul,
But hollow shells, as empty as the whole.
In tangled webs of artifice we're caught,
By our own hands, the noose of fate is wrought.
As God did cast Prometheus from the skies,
We bind ourselves in chains of our own lies.
All just patterns, like woven silk, we spin,
Entangled dreams, mere shadows of our kin;
For in the end, the art we do create,
Is but reflection of our human state.
Re: Testing GPT 4's code-writing capabilities with some real world problems
#454Earlier quoted context omitted.
I think the fear should be less about AI taking 100% of jobs but it should be AI making a single programmer do the job of 5, which would wipe a majority of the market out and make it a non-viable career option for most. Companies are already bloated, imagine when they realize one overworked highly paid senior can replace 10 juniors.
How much more efficient is programming in Python with modern tools vs assembly? I would bet more than 5x
Re: Testing GPT 4's code-writing capabilities with some real world problems
#455I have two tasks I wanted it to try, both making use of public APIs, starting from scratch. In short, it was frustrating as hell. Never-ending import problems -- I'd tell it the error, it'd give me a different way to import, only leading to a new import problem. I think I used up all my 100 queries in 4 hours of GPT-4 just on the import/library problem.
Then there were constant mis-use of functions -- ones that didn't exist, or didn't exist in the object it was using, but did exist in some other object instead, at which point it would apologize and fix it (why didn't you give it to me correct the first time, if you "know" the right one?)
The actual code it wrote seemed fine, but not what I'd call "scary impressive." It also kept writing the same code in many different styles, which is kind of neat, but I found one style I particularly liked and I don't know how to tell it to use that style.
Lastly, it's only trained up to Sep 2021, so all the APIs it knew were well behind. I did manage to tell it to use an updated version, and it seemed to oblige, but I don't really know if it's using it or not -- I still continued to have all the above problems with it using the updated API version.
Anyway, I hope MS fiddles with it and incorporates it into Visual Studio Code in some clever way. For now, I'll continue to play with it, but I don't expect great things.
Re: Testing GPT 4's code-writing capabilities with some real world problems
#456In before all the comments about how “most code is trivial” or “most programming is stuff that already exists” or “you’re missing the point look how it’s getting better”. I really am in awe of how much work people seem willing to do to justify this as revolutionary and programmers as infantile, and also why they do that. It’s fascinating. Thinking back to my first job out of college as a solid entry level programmer.…
While I think there's truth to what you say, I'd also point our that workers in many pre-automated industries with an "artisan" approach also considered themselves irreplaceable because they figured, correctly, that nobody could build a machine with the capability of reproducing their workflow, with all its inherent uncertainty, flexibility and diverse physical and mental skills. What they failed to predict was that…
Re: Testing GPT 4's code-writing capabilities with some real world problems
#457I want to see GPT-4 dealing with this situation: - they: we need a new basic POST endpoint - us: cool, what does the api contract look like? URL? Query params? Payload? Response? Status code? - they: Not sure. Third-party company XXQ will let you know the details. They will be the ones calling this new endpoint. But in essence it should be very simple: just grab whatever they pass and save it in our db - us: ok, cool…
This is also one of the reasons India taking over all of the programming work didn’t really happen. There are numerous issues (time zones, language, etc.) but business people not being able to document perfectly what they want to have built, considering all corner cases and paths, is a big one.
Re: Testing GPT 4's code-writing capabilities with some real world problems
#458Re: Testing GPT 4's code-writing capabilities with some real world problems
#459Earlier quoted context omitted.
I think the fear should be less about AI taking 100% of jobs but it should be AI making a single programmer do the job of 5, which would wipe a majority of the market out and make it a non-viable career option for most. Companies are already bloated, imagine when they realize one overworked highly paid senior can replace 10 juniors.
If increased productivity equaled job loss, there would be two programmers alive today, doing the same job as the fewer than 10000 programmers using punch cards as we entered the year 1950. A lot of projects today are not even greenlit because they would be too expensive to make. For instance, there are a lot processes in almost every country that require you to file paper forms, even though we have had web forms and…
Yeah. The problem is that there’s only one of me. All the rest of you are filling in for the other guy.
Re: Testing GPT 4's code-writing capabilities with some real world problems
#460I want to see GPT-4 dealing with this situation: - they: we need a new basic POST endpoint - us: cool, what does the api contract look like? URL? Query params? Payload? Response? Status code? - they: Not sure. Third-party company XXQ will let you know the details. They will be the ones calling this new endpoint. But in essence it should be very simple: just grab whatever they pass and save it in our db - us: ok, cool…
Yes it can write code, some demoed developing "Doom", ray tracing/ray casting with GPT-4 the very first day it came out and it was impressive. Programmers would still program, but the program will no longer be code but will be "GPT prompts". I suspect with time tho, we won't need to write amazing prompts, you ask GPT for a solution, it will then figure out the edge cases by asking you questions. If it's 2 people, it…