this post was submitted on 24 Nov 2023
-2 points (49.5% liked)

Technology

59207 readers
3474 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 16 points 11 months ago* (last edited 11 months ago) (4 children)

Even if ChatGPT gets far in advance of the way it is now in terms of writing code, at the very least you're still going to need people to go over the code as a redundancy. Who is going to trust an AI so much that they will be willing to risk it making coding errors? I think that the job of at the very least understanding how code works will be safe for a very long time, and I don't think ChatGPT will get that advanced for a very long time either, if ever.

[–] [email protected] 18 points 11 months ago (1 children)

There's more to it than that, even. It takes a developer's level of knowledge to even begin to tell ChatGPT to make something sensible.

Sit an MBA down in front of a ChatGPT window and tell them to make an application. The application has to save state, it has to use the company's OAuth login system, it has to store data in a PostgreSQL database, and it has to have granular, roles-based access control.

Then watch the MBA struggle because they don't understand that...

  • Saving state is going to vary depending on the front-end. Are we writing a browser application, a desktop application, or a mobile application? The MBA doesn't know and doesn't understand what to ask ChatGPT to do.
  • OAuth is a service running separately to the application, and requires integration steps that the MBA doesn't know how to do, or ask ChatGPT to do. Even if they figure out what OAuth is, ChatGPT isn't trained on their particular corporate flavor for integration.
  • They're actually writing two different applications, a front-end and a back-end. The back-end is going to handle communication with PostgreSQL services. The MBA has no idea what any of that means, let alone know how to ask ChatGPT to produce the right code for separate front-end and back-end features.
  • RBAC is also probably a separate service, requiring separate integration steps. Neither the MBA nor ChatGPT will have any idea what those integration steps are.

The level of knowledge and detail required to make ChatGPT produce something useful on a large scale is beyond an MBA's skillset. They literally don't know what they don't know.

I use an LLM in my job now, and it's helpful. I can tell it to produce snippets of code for a specific purpose that I know how to describe accurately, and it'll do it. Saves me time having to do it manually.

But if my company ever decided it didn't need developers anymore because ChatGPT can do it all, it would collapse inside six months, and everything would be broken due to bad pull requests from non-developers who don't know how badly they're fucking up. They'd have to rehire me... And I'd be asking for a lot more money to clean up after the poor MBA who'd been stuck trying to do my job.

[–] [email protected] 4 points 11 months ago (1 children)

Thank you, you explained all of that much better than I could.

[–] [email protected] 7 points 11 months ago

You're welcome! And it occurs to me that the fact that it took a developer to explain all of that is an object lesson in why ChatGPT won't end software development as a career option - and believe me, I simplified it for a non-developer audience.

[–] [email protected] 15 points 11 months ago (1 children)

Who is going to trust an AI so much that they won't risk it making coding errors?

Sadly, too many

[–] [email protected] 3 points 11 months ago (2 children)

Then their companies will go belly-up.

[–] [email protected] 8 points 11 months ago (1 children)

I don't believe it. If it's good enough then they will ship and make money, and those who put people on it will be so slow that they will be just outperformed by those who don't.

[–] [email protected] 6 points 11 months ago (1 children)

If your code doesn't work because you rely entirely on an AI to do it, you don't have a business you can run unless you want to go back to paper and pencil.

[–] [email protected] 0 points 11 months ago (1 children)

If your code doesn't work because you rely on humans understanding it, you don't have a business you can run. We already are there where humans have no idea why the computer does this or that decision because it's so complex especially with all the machine learning and complex training data, etc. let's not pretend it will get less complex with time.

[–] [email protected] 3 points 11 months ago (2 children)

So your argument is that people will rely on AI entirely without making any redundancies, unlike now where they have more than one human so they can check for these issues because humans make coding errors?

[–] [email protected] 1 points 11 months ago (2 children)

My argument is that already today no human is able to and checks it when it comes to decision making models like for example if the car should go left or right around a obstacle. And over time we will have less straight forward classical programming doing decisions and more and more models doing decisions with hundreds or thousands of sensor inputs.

[–] [email protected] 3 points 11 months ago (1 children)

And that means AI code shouldn't be error-checked?

[–] [email protected] 1 points 11 months ago (2 children)

That means that it right now can not be error checked and it will be even more difficult in the future.

[–] [email protected] 2 points 11 months ago (1 children)

So you're saying no code would be worth error checking by a human at all? There is no level of simpler code that an AI could get wrong and would need someone to fix it?

[–] [email protected] 1 points 11 months ago (2 children)

My assumption is that it would even be the other way around, AI checking all human code, especially writing all the tests. So I guess AI would also write tests for it's own code too.

When it comes to humans, I think they would probably be changing the prompt they give to AI instead of changing the code at the end. You can already see how it's done with generation of pictures, while theoretically you could take a not so perfect AI picture and use Photoshop to fix it, but most of the time people change the prompt instead and regenerate the picture.

[–] [email protected] 3 points 11 months ago (1 children)

The generation of pictures is full of fuckups like giving people extra legs, so I'm not sure that's a very good example.

[–] [email protected] 0 points 11 months ago (1 children)

I'm not sure why you think it's not a good example. The picture itself is code (PNG, JPEG, etc.) which some AI wrote and no human at the company has checked but it gets delivered to the customer who pays for it. It's not as good as if a human would do it, but it's way way way cheaper so you can generate a couple of times until you get what you want. So in this domain humans already are losing jobs to AI even though AI is so bad that it is giving people extra legs, etc.

The same thing happens with hallucinations of ChatGTP, which despite that is still preferable by customers to a human assistant who would summarize articles, etc. with much better quality but very low speed and very expensive.

Code is not much different from summaries of longer texts.

[–] [email protected] 1 points 11 months ago (1 children)

What human has lost their job to AI image creation?

[–] [email protected] 2 points 11 months ago (1 children)
[–] [email protected] 1 points 11 months ago (1 children)

That article says artists are still needed to touch up the AI art, which was my whole point about people who understand code, so I think you just proved my point.

[–] [email protected] 1 points 11 months ago (1 children)

Ok, if your point was that instead of 90 junior programmers and 10 senior programmers before, now the 10 senior programmers will keep their job and instead of touching up the juniors code they touch up the AIs code then yes you're right, those jobs will be kept for some more time.

[–] [email protected] 1 points 11 months ago (1 children)

My point:

Even if ChatGPT gets far in advance of the way it is now in terms of writing code, at the very least you’re still going to need people to go over the code as a redundancy.

Note I never said anything about the number of people.

Maybe you should read before responding.

[–] [email protected] 1 points 11 months ago

Ok, I will do that next time ...

[–] [email protected] 1 points 11 months ago (1 children)

Until even the tests are bugged

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (1 children)

Have you seen tests written by humans? 😅

[–] [email protected] 1 points 11 months ago
[–] [email protected] 1 points 11 months ago

Or let me rephrase it with the context of the original assumption that if people don't check the code which AI wrote the company will lose customers because the quality is bad.

Right now there are tons of models out there which no human can understand why they decide this or that, still they bring so much more value that they get shipped even though they make some mistakes. If a company would try to only ship code checked by humans they would not be able to ship the products and would lose their customers to a company which does not check it but does ship.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

Except we already have fields (like pharma manufacturing) that have to deal with hundreds or thousands of inputs and variables, are automated, and we still manage to fully understand the stack as well as fully check everything.

Hint: when someone tells you they "can't" check or understand what their software is doing, it's a scam.

Normally they should be told to go back and figure it out before being allowed to ship any product. If you tried this in any other industry it would be laughable. Even in software it's outrageous, imagine getting accounting software or even a simple file backup tool that doesn't work some of the time and nobody can tell you how it works. Yet these companies get a pass putting cars like this on the road.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

I kinda agree with them. Currently coding already is an abstraction. The average developer has very little idea what machine code their compiler actually produces, and for the most part they don't need to care about this. Feeding an AI a specification is just a higher level of abstraction.

For now, we'll need people to check that AI produces code that does what we expect, but I believe at some point we'll mostly take it for granted that they just do.

[–] [email protected] 1 points 11 months ago

I'd hope so, but it already works for many of them

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (1 children)

That's a fuckin bleak outcome for a lot of people if the job transition goes from \ to \

That's like being an artist and being told your job now is simply to fix the shitty hands Midjourney draws. And your job will only last as long as that remains a problem.

[–] [email protected] 5 points 11 months ago

Hey, I didn't say the future would be bright, just that it will still need people familiar with code for the foreseeable future. At least until the Earth heats up so much that the lack of potable water and the unsurvivable high temperatures destroy civilization.

[–] [email protected] 2 points 11 months ago

It isn't surprising that this is the way we conceptualize the potential impact of AI, but it's frustrating to see it tossed around as if AI disruption is a forgone conclusion.

AI will start re-defining the problems that code is written to solve long before we get anywhere close to GPT models replacing human workers, and that's a big enough problem by itself.

It used to be that before code could even be employed to solve a problem, it had to be understood procedurally. That's increasingly not the case, given that ML is routinely employed to decode things that were previously thought to be too chaotic to be understood, like brain waves and image pixel data. I don't know why we're so sure of ourselves that machine learning is just a gimmick and poses no real threat, just because anthropomorphizing it seems silly.