Technology

87080 readers

3782 users here now

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

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago

MODERATORS

L3s@lemmy.world

enu@lemmy.world

technopagan@lemmy.world

L4s@lemmy.world

L3s@hackingne.ws

421

AI code increasingly leads to production failures (www.heise.de)

submitted 2 months ago by HaraldvonBlauzahn@feddit.org to c/technology@lemmy.world

32 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Repelle@lemmy.world 30 points 2 months ago (1 children)

This is what happens when increased velocity is demanded. It takes at least as long to verify that the code works well as it would have for me to write and verify. I can pump out a ton of code with an LLM, but if you want quality it’ll take me just as long as 2 years ago, probably longer because of my decreased practice lately

[–] logi@lemmy.world 22 points 2 months ago* (last edited 2 months ago)

It was established decades ago that

It’s harder to read code than to write it.

Joel Spolsky

and

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.

Brian Kernighan

Having lots of code appear out of thin air isn't really of any help in making functional systems.