4 ms·

I've tried Copilot the last week and am severely underwhelmed. Many of suggestions don't make any sense and it takes me more time to analyze and disregard the w

I've tried Copilot the last week and am severely underwhelmed. Many of suggestions don't make any sense and it takes me more time to analyze and disregard the wrong ones than it saves me time. Most egregious though is that it suggests invalid code, i.e. code that can't be compiled. For example it suggests a setter that doesn't exist. I don't know if I'm using it wrong but right now it's not even worth the free trial for me. I'm not sure if Kodezi is any better. But the page as so often doesn't provide me with enough information without having to sign up and try it myself. Wanna know what "Debug bugs" actually looks like? Sure, watch this short styled up video which actually doesn't show anything. I found some information in the doscs https://docs.kodezi.com/feature-guides/debugging https://docs.kodezi.com/feature-guides/debugging but that's a manual, not a proper feature presentation.

jcq3 4y ago
If you expect AI to generate a complete project bug free from one line comment, yes it will need some time before that happens. Github co-pilot has been a game changer for me just because it allows me to code 20%-30% faster. As SWE our only way to scale is by improving our productivity and spend less time writing casual snippets of code.
- usgroup 4y ago
  Well we have many ways to do it by abstraction — libraries, recipes, patterns, and so on. I think that this sort of thing will handicap a dev in the same way that learning to write with a spell checker can (does!) handicap writers.
- louthy 4y ago
  Coding speed is absolutely not the problem that needs solving. What is needed is how to do more with less code. Long term maintenance of massive code-bases is the hard bit that eats away at productivity.
  - 6gvONxR4sf7o 4y ago
    Writing unit tests faster absolutely encourages me to write more thorough tests. It’s less about speed to me and more about painlessness. It’s good at the most boring snippets, which I’m happiest to offload. Treat it as a mildly better autocomplete, and you’ll be happy with it.
- jossclimb 4y ago
  This is how I use it. I ignore anything specific to the logic of what I am writing, but it's great for filling out shit like structs and gets those right. I start typing `type ResponseHandler....` and it immediately knows what I want
serpix 4y ago
for me the Copilot killer feature is its ability to learn from context. If I write a function and then use that function later copilot learns how I use the function and suggests the correct parameters and even knows to change some of the parameters depending on the context. In this way it is jaw dropping and a serious multiplier to productivity.
sinuhe69 4y ago
Same issue I faced with Tabnine. I'm coding in many languages simultaneously, and I noticed that Tabnine produced often invalid code, suggested functions which are non-existing at all.

jcq3 4y ago

If you expect AI to generate a complete project bug free from one line comment, yes it will need some time before that happens. Github co-pilot has been a game changer for me just because it allows me to code 20%-30% faster. As SWE our only way to scale is by improving our productivity and spend less time writing casual snippets of code.

usgroup 4y ago
Well we have many ways to do it by abstraction — libraries, recipes, patterns, and so on. I think that this sort of thing will handicap a dev in the same way that learning to write with a spell checker can (does!) handicap writers.
louthy 4y ago
Coding speed is absolutely not the problem that needs solving. What is needed is how to do more with less code. Long term maintenance of massive code-bases is the hard bit that eats away at productivity.
- 6gvONxR4sf7o 4y ago
  Writing unit tests faster absolutely encourages me to write more thorough tests. It’s less about speed to me and more about painlessness. It’s good at the most boring snippets, which I’m happiest to offload. Treat it as a mildly better autocomplete, and you’ll be happy with it.
jossclimb 4y ago
This is how I use it. I ignore anything specific to the logic of what I am writing, but it's great for filling out shit like structs and gets those right. I start typing `type ResponseHandler....` and it immediately knows what I want

serpix 4y ago

for me the Copilot killer feature is its ability to learn from context. If I write a function and then use that function later copilot learns how I use the function and suggests the correct parameters and even knows to change some of the parameters depending on the context. In this way it is jaw dropping and a serious multiplier to productivity.

sinuhe69 4y ago

Same issue I faced with Tabnine. I'm coding in many languages simultaneously, and I noticed that Tabnine produced often invalid code, suggested functions which are non-existing at all.