Re:I tested Copilot in an existing open-source codebase with...
by byteface on Sunday August 15, 2021 @04:32PM
(#28192263)
He seems to know the codebase and works out the problem for about 30 mins sometimes fastfowarded. Then at about 28 mins copilot smashes the answer instantly when he types a method name at the bottom of a utils file.
he doesn't like it though as he seems to know the api really well and wants the util to use his api instead. so deletes the copilot answer and types out a different answer using the api which he knows.
then creats a few unit tests.
This was an interesting watch and useful to see other peoples setups.
Re:I tested Copilot in an existing open-source codebase with...
by hdjjhhvvhga on Monday August 16, 2021 @06:42AM
(#28196673)
But the value for who? Last time I checked the consensus was that using it in any project that is not for private use can get you in legal trouble. So for me it's completely useless, even if technically it could be improved with time (which may or may not happen).
Re:I tested Copilot in an existing open-source codebase with...
by yourapostasy on Monday August 16, 2021 @06:35PM
(#28203814)
> But the value for who?
Presumably value "unlocked" for GitHub investors, by leveraging the ML model that drives some product based upon Copilot like a next-gen IDE. I agree it's not a good risk to assume for the users of Copilot.
Seems to me that once you can go either way then you just proved the other redundant.
https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste...
^ where the 'unit' is basically a function. i.e., to test a function fully, write a test as complicated as the function
then creats a few unit tests.
This was an interesting watch and useful to see other peoples setups.
Presumably value "unlocked" for GitHub investors, by leveraging the ML model that drives some product based upon Copilot like a next-gen IDE. I agree it's not a good risk to assume for the users of Copilot.