@enkiv2 I feel like for me copilot was barely useful for writing new code, but super useful for writing unit tests, which are 90% boiler plate and repetitive (but I think that's in a good way)
Conversation
Notices
-
Remco van Bree (blikkie@hachyderm.io)'s status on Saturday, 15-Jul-2023 13:47:30 UTC Remco van Bree -
ð’€ð’‚—ð’† (enkiv2@eldritch.cafe)'s status on Saturday, 15-Jul-2023 13:47:31 UTC ð’€ð’‚—ð’† the fact that some people find LLMs useful for writing code is not a credit to LLMs but an indictment of the average signal to noise ratio of code: it means that most code is confusing boilerplate -- boilerplate because a statistical model can only reliably reproduce patterns that reoccur many times across its training corpus, and confusing because otherwise-intelligent people capable of convincing a hiring manager that they are competent programmers find it easier to ask a statistical model to produce an incorrect prototype they must debug than write the code themselves. we all know from experience that most code is bad, but for LLMs to be able to write more-or-less working code at all indicates that code is much worse than we imagine, and that even what we consider 'good' code is from a broader perspective totally awful. (in my opinion, it is forced to be this way because of the way we design programming languages and libraries.)
-