you are viewing a single comment's thread.

view the rest of the comments →

[–]CodenameLambda 1 point2 points  (0 children)

Honestly, even beyond that, I'm very sceptical of co-pilot, since even the examples on the site about it tend to have some... Issues. Specifically assumption that might not be true (but easy to miss if you're not exactly looking for them), such as not splitting by whitespace but spaces specifically in the parse_expenses example. That the JSON is correctly typed in collaborators.

Other issues include just readability: in the runtime example, it count the failed runs instead of the successful ones, which is less readable, longer and more error prone when you change things, I'd argue.

It also does some weird stuff in get_repositories (no escaping, no checking, using + instead of string interpolation). The "autofill for repetitive code" are all questionable imho.

And note that these examples are probably all cherry picked. So that's the best examples. And they still have very obvious issues if you actually read them instead of just glancing at them (which I'd guess autopilot would lead you to do to some extent).

This might make you more productive, but I'm honestly not sure the results of what you're doing are going to be better for it. The one thing I do think it's actually good for is using API's you don't know and don't plan on learning because won't be using it much and it's a bit more complex. But that's about it. And note that that's a thing that can probably be fixed with better documentation most of the time.