"This code is giving me a return value of X instead of Y"
"Ah the reason you're having trouble is because you initialized this list with brackets instead of new()."
"How would a syntax error give me an incorrect return"
"You're right, thanks for correcting me!"
"Ok so like... The problem though."
Not copilot, but I run into a fourth problem:
4. The LLM gets hung up on insisting that a newer feature of the language I'm using is wrong and keeps focusing on "fixing" it, even though it has access to the newest correct specifications where the feature is explicitly defined and explained.
They just brought back print and it's been very satisfying for me so far.
How very big money of you.
Does macOS respond to external keyboard power button presses because if so this could very well be as easy money-making real product
I do try to keep the "unknown unknowns" problem in mind when I use it, and I've been using it far less as I latched on to how OOP actually works and built up the lexicon and my own preferences. I try to only ask it for high-level stuff that I can then use to search the wider (hopefully more human) internet more traditionally with. I fully appreciate that it's nothing more than a very incredibly fancy auto-completion engine and the basic task of auto-complete just so happens to appear intelligent as it gets better and more complex but continues to lack any form of real logical thoughts.
I believe accessibility is the part that makes LLMs helpful, when they are given an easy enough task to verify. Being able to ask a thing that resembles a human what you need instead of reading through possibly a textbook worth of documentation to figure out what is available and making it fit what you need is fairly powerful.
If it were actually capable of reasoning, I'd compare it to asking a linguist the origin of a word vs looking it up in a dictionary. I don't think anyone disagrees that the dictionary would be more likely to be fully accurate, and also I personally would just prefer to ask the person who seemingly knows and, if I have reason to doubt, then go back and double-check.
Here's the manpage for bash's statistics from wordcounter.net:
Understood, thanks for the info. Probably worth raising with them on the discord, which I would do if I felt strongly about it.
https://thunderstore.io/c/lethal-company/p/ebkr/r2modman/v/3.1.45/
Edit, for convenience:
(Emphasis mine, one of them humorous. There's more, but formatting this on my phone is tedious and frustrating.)
Haha, yeah. It really loves to refactor my code to "fix" bracket list initialization (e.g. List<string> stringList = [];) because it keeps not remembering that the syntax has been valid for a while.
It's newest favorite hangup is to incessantly suggest null checks without asking if it's a nullable property that it's checking first. I think I'm almost at the point where it's becoming less useful to me.
Happy to help!