Programming

17420 readers

92 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Why Copilot is Making Programmers Worse at Programming (www.darrenhorrocks.co.uk)

submitted 2 months ago by [email protected] to c/[email protected]

54 comments fedilink hide all child comments

Over the past few years, the evolution of AI-driven tools like GitHub’s Copilot and other large language models (LLMs) has promised to revolutionise programming. By leveraging deep learning, these tools can generate code, suggest solutions, and even troubleshoot issues in real-time, saving developers hours of work. While these tools have obvious benefits in terms of productivity, there’s a growing concern that they may also have unintended consequences on the quality and skillset of programmers.

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

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

You write machine code?

No, you only describe what you want the compiler to write in machine code.

With copilot it's still a description.

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

Copilot frequently produces results that need to be fixed. Compilers don’t do that. Anyone who uses copilot to generate code without understanding how that code works is a shit developer. The same is true of anyone who copies from stack overflow/etc without understanding what they’re copying.

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

You're missing the point. If the program doesn't do what it's meant to its YOU that didn't use the tools between you and metal, correctly. LLM involved or not, it's how you've described it, in whatever 'language' you chose (natural or Rust)

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

The key difference is that compilers don’t fuck up, outside of the very rare compiler bug. LLMs do fuck up, quite often.

load more comments (8 replies)