3 ms·

This was my experience as well. The time it saved me didn't add up to the time I spent in the debugger fixing subtle bugs in code that looked fine but didn't qu

• macNchz 3y ago
  I think there’s a “eyes glaze over” effect with generating lots of boilerplate, where things look generally correct, but have issues you need to be paying attention to notice and correct. One example recently: I watched a developer scaffolding a database schema with an ORM. Plenty of boilerplate defining the fields and stuff, nice to have Copilot running, however the suggestions were baking in bad design that would work now, but almost certainly cause pain later: nullable foreign keys, text fields with inappropriate max lengths, redundant FK relationships where a relationship could be ambiguous depending on whether you joined directly on the FK or through another related table, etc. Obviously all of that is on the developer to notice and be responsible for, but it’s really easy to just tab through the completions, see that it works (right now) and move on.