3 ms·

Slightly off topic, but I seriously wonder if copilot/other AI coding tools are going to end up a one way street, in the sense that one would be able to write t

by yumraj 3y ago

Slightly off topic, but I seriously wonder if copilot/other AI coding tools are going to end up a one way street, in the sense that one would be able to write the v1 of the product, but will end up being maintenance nightmare since no one, not even the original author/ copilot-driver , would have an idea how things work and fit together.

ulizzle 3y ago
I've never seen GH Copilot use "tmpVar1" and "tmpVar2" as variable names or "ijk" for-loops. That is a step above the average human programmer as-is. The dream is that you write the method names and the A.I writes the code for you.
9dev 3y ago
I doubt you’ve ever really worked with Copilot on your own. It doesn’t write the entire application for you, but mostly completes the line you were about to write anyway. It’s not a tool ideal for beginners; but then again, an app written by a junior will end up a maintenance nightmare whether they have Copilot or not. The fear of this thing is so much overblown, it’s ridiculous.
- yumraj 3y ago
  Yes, you're right that I have not worked with Copilot. But, I'm not afraid of it and am currently trying to run Code Llama locally. Am definitely looking forward to learn more. Having said that, I have seen contradictory statements on how people are using these, or see themselves using these. One is the way you mentioned, completing line or perhaps writing complete functions given a prompt. However, people, including in this thread, have talked about working in new frameworks etc. which implies to me that they are probably using copilot to generate much of the code. I have had conversation with non-Engineers (read Product Manager types), who are using it to generate code and write applications. And, that is the situation I was referring to becoming a maintenance nightmare. The way I see it, it's just a tool. It can be great in the hands of an experienced programmer, but might become a deadly weapon in the hands of a novice.

by yumraj 3y ago

ulizzle 3y ago

I've never seen GH Copilot use "tmpVar1" and "tmpVar2" as variable names or "ijk" for-loops. That is a step above the average human programmer as-is. The dream is that you write the method names and the A.I writes the code for you.

9dev 3y ago

I doubt you’ve ever really worked with Copilot on your own. It doesn’t write the entire application for you, but mostly completes the line you were about to write anyway. It’s not a tool ideal for beginners; but then again, an app written by a junior will end up a maintenance nightmare whether they have Copilot or not. The fear of this thing is so much overblown, it’s ridiculous.

yumraj 3y ago
Yes, you're right that I have not worked with Copilot. But, I'm not afraid of it and am currently trying to run Code Llama locally. Am definitely looking forward to learn more. Having said that, I have seen contradictory statements on how people are using these, or see themselves using these. One is the way you mentioned, completing line or perhaps writing complete functions given a prompt. However, people, including in this thread, have talked about working in new frameworks etc. which implies to me that they are probably using copilot to generate much of the code. I have had conversation with non-Engineers (read Product Manager types), who are using it to generate code and write applications. And, that is the situation I was referring to becoming a maintenance nightmare. The way I see it, it's just a tool. It can be great in the hands of an experienced programmer, but might become a deadly weapon in the hands of a novice.