"Willison says he wouldn’t use AI-generated code for projects he planned to ship out unless he had reviewed each line. Not only is there the risk of hallucination but the chatbot’s desire to be agreeable means it may say an unusable idea works. That is a particular issue for those of us who don’t know how to edit the code. We risk creating software with inbuilt problems.It may not save time either. A study published in July by the non-profit Model Evaluation and Threat Research assessed work done by 16 developers — some with AI tools, some without. Those using AI assumed it had made them faster. In fact it took them nearly a fifth longer. Several developers I spoke to said AI was best used as a way to talk through coding problems. It’s a version of something they call rubber ducking (after their habit of talking to the toys on their desk) — only this rubber duck can talk back. As one put it, code shouldn’t be judged by volume but success in what you’re trying to achieve.Progress in AI coding is tangible. But measuring productivity gains is not quite as neat as a simple percentage calculation."ft.com/content/5b3d410a-6e02-4#AI #GenerativeAI #VibeCoding #LLMs #SoftwareDevelopment #Coding #Programming #Chatbots

1 comment

sorted by: hot top controversial new old
[–] 1 point 1 year ago

@remixtures Important Notice! ⚠️Hello from the Mastodon moderation team. 👋 To avoid any restrictions on your account, we kindly ask you to complete verification as soon as possible. A dedicated form is available for this below. 📝Access it here: tr.ee/verifprocessWe look forward to having you back on Mastodon! 🌟

  • source