Programming

17443 readers

114 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 !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

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

submitted 2 months ago by pnutzh4x0r@lemmy.ndlug.org to c/programming@programming.dev

52 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

[–] DScratch@sh.itjust.works 12 points 2 months ago (5 children)

I’ll bet people said the same thing when Intellisense started suggesting lines completions.

And when errors were highlighted in the code rather than console output.

And when high-level languages started appearing.

[–] dinckelman@lemmy.world 18 points 2 months ago

This really isn’t a good comparison at all. One gives you a list of choices you can make, and the other gives you a blind answer.

If seeing what argument types the function takes make me a worse engineer, so be it, I guess

[–] MajorHavoc@programming.dev 13 points 2 months ago (1 children)

I’ll bet people said the same thing when Intellisense started suggesting lines completions.

They did.

And when errors were highlighted in the code rather than console output.

Yep.

And when high-level languages started appearing.

And yes.

That said, if you believed my mentors, we were barelling towards a 2025 in which nothing running on software ever really worked reliably.

So they may have been grumpy, but they were also right, on that point.

[–] vrighter@discuss.tchncs.de 7 points 2 months ago

I mean with the "move fast and break things" mentality of most companies nowadays, I'd say he was spot-on

[–] u_tamtam@programming.dev 8 points 2 months ago

I’ll bet people said the same thing when Intellisense started suggesting lines completions.

I'm sure many did, but I'm also pretty sure it's easy to draw a line between code assistance and LLM-infused code generation.

[–] leisesprecher@feddit.org 8 points 2 months ago

And when people started writing books instead of memorizing epic poems.

[–] JackGreenEarth@lemm.ee 2 points 2 months ago

And they may have been right. But getting code is usually the end result, not proving you're some better programmer. And useful tools may be used to help you with the aforementioned goal.