zlacker

I have to be honest I've not used it but it truly sounds incredible that it can do things as well as you say.

So you write tests and copilot generates code you shove into production with little overhead ?

Do you read the code thoroughly (kind of negating having it generated for you?), or just have blind faith in it because tests are green and just YOLO it into production ?

I'd feel pretty uneasy deploying code that:

  * I, or a trusted peer has not written.

  * Hasn't been reviewed by my peers.

  * Code I, or my peers don't understand fairly well.

That's not to say I think me or my colleagues write code that doesn't have problems, but I like to think we at least understand the code we work with and I believe this has benefits beyond just getting stuff done quickly and cheaply.

In other words, I have no problem using code generated by co-pilot, but I'd feel the need to read and review it quite thoroughly and then I sort of feel that negates the purpose, and it also means it pulls my back into the role of doing work I'd hire someone else to do.

>>bamboo+(OP)
But I do review and test it and it is mostly 80% ok. It even learns your style of coding. Like said; it works best for stuff that is heavy on code but low on thought.

>>tluybe+oa3
Do you enjoy working like this? Having CP generate things correctly 80% of the time and then having to scrutinize whatever is generated and look for problems?

Genuine question, not being snarky.