251–260 of 1001 posts
Calling it now, there will be a "Copilot considered harmful" post. If you need to go through the suggested code to ensure it's correct, you may as well write it yourself? If you glance at it and it looks about right, you can potentially overlook bugs or edge cases, you'll lose confidence in your own code since you didn't properly conceptualise it yourself. Potentially for newer developers it robs them of active exper…
Honestly, this attitude (dismissing the feature even without trying it out) comes across as insecurity and gatekeeping.
I remember another company called Kite [1], working on a similar approach - smart autocompletion - this however uses GPT-3 so it's a bit different I guess because it doesn't detect what you're trying to do but rather transforms technical natural language into code. Right? [1] https://www.kite.com
Earlier quoted context omitted.
Lots of questions: - the generated code by AI belongs to me or GitHub? - under what license the generated code falls under? - if generated code becomes the reason for infringment, who gets the blame or legal action? - how can anyone prove the code was actually generated by Copilot and not the project owner? - if a project member does not agree with the usage of Copilot, what should we do as a team? - can Copilot copy…
You should read the FAQ at the bottom of the page; I think it answers all of your questions: https://copilot.github.com/#faqs
Earlier quoted context omitted.
How many jobs have developers helped displace in business and industry? I don't think it's controversial that we become fair game for that same automation process we've been leading.
> How many jobs have developers helped displace in business and industry? How many? > I don't think it's controversial that we become fair game for that same automation process we've been leading. This is not correct. A human (developer) displacing another human (business person) is entirely different than a tool (AI bot) replacing a human (developer). Regardless, this is the Lump of Labour fallacy ( https://en.wikip…
That's not what is happening though, a few developers replace thousands of business and industry people with automated tools. Say, automated route planning for package delivery, would take many thousands of humans if not for the AI bots that do the job instead.
> SWE is a complex field, way more than typing a few routines. In best case (technologically speaking) this will be an augmentation.
Of course there will always be some jobs for humans to do. Just like there are still jobs for humans loading thread into the automated looms and such.
But your arguments against automation displacing programming jobs ring hollow. People said the same thing about chess playing programs, they would never be able to understand the subtlety or complexity like a human could.
Earlier quoted context omitted.
What do you think about this being overall detrimental to code quality as it allows people to just blindly accept completions without really understanding the generated code. Similar to copy-and-paste coding. The first example parse_expenses.py uses a float for currency - that seems to be a pretty big error that's being overlooked along with other minor issues around no error handling. I would say the quality of the…
Why would you say it's an error to use a float for currency? I would imagine it's better to use a float for calculations then round when you need to report a value rather than accumulate a bunch of rounding errors while doing computations.