When I post a technical question in Forums, I usually add something like "Tried Copilot, got useless answer ...". The trouble with asking an LLM is that there are a huge number of people (this predates LLMs) who post answers on forums along the lines of "turn it off and turn it on again" LLMs pick that up as the consensus solution.

▲

zem 2 days ago | parent | next [-]

I ran into a pretty funny instance just yesterday - I was upgrading my windows partition to windows 11 and I asked claude if there was any chance it could corrupt my linux partition in the process. claude confidently said that yes there was a known failure mode where if the recovery partition was not large enough for windows 11 it would silently resize it, damaging the neighbouring partition. it even told me what system command it used to do so.

I googled the command and when the gemini prompt came up I said that claude had told me it might be run during the upgrade and damage my linux partition. gemini said "there is no such argument to that program, the other AI is hallucinating, and here is the knowledge base article that probably caused it to go wrong", which was actually pretty impressive, and amusing in the way it used both the term "hallucinating" and the phrase "the other AI".

▲

II2II 4 days ago | parent | prev | next [-]

Something tells me people's milage varies based upon how they prompt the LLM. I spent about half an hour using traditional web searches to tackle a software configuration problem today, then about another half an hour poking around the system to see if I could find a solution, then about half an hour with an LLM. Not once was I told by the LLM to use the consensus solution of reinstalling the operating system even though it was clearly bumbling around much as I was earlier. (Eventually I decided to go with the consensus decision.)

▲

BobbyTables2 4 days ago | parent | prev | next [-]

I actually hate reading posts that go “I can’t understand/fix this problem. Tried LLM…”

To me, such screams “I’m too lazy to do anything more than ask a LLM. I’ve tried nothing and I’m all out of ideas”

Show me you put a modicum effort and aren’t just looking to be spoon-fed the content from the first Google result that would have been found.

▲

jagged-chisel 4 days ago | parent [-]

I get exasperated with the inexperience that I have run across for decades. Yes, I frobnicated the frobnitz, I transmogrified the bit twiddler, I wizzled the wobnosticator, (and this decade, I talked the three LLMs), and the problem still exists. What I really need to know is how the transmogrification affects frobnication, but no one has ever touched that configuration.

“Why would you even want to do that?”

I dunno, man, it’s the job I was given. Do you know or not? No. No one does.

I take a week to figure it out, I come back to the forum to post my response, and it’s automatically closed as off-topic.

*sigh*

▲

theamk 2 days ago | parent [-]

> Why would you even want to do that?”

> I dunno, man, it’s the job I was given. Do you know or not?

That's pretty sad to hear, and that's the hardest thing about working with junior engineers (or nowadays, with LLMs). Someone made a wrong assumption that a thing is possible, gave the wrong instructions, or simply phrased things badly, and now that person (or LLM) is trying to solve the impossible task instead of exploring the alternative approaches.

If it's LLM, the solution is simple. For a human, I usually bypass them and go to their senior directly: "Hey, did you task jagged-chiesel to transmogricate the frobnicator? This is a pretty complex task and our transmogricators are not trally desinged to work on frobs. What was the task you were trying to solve? Perhaps it's time to look into fizz-buzzing instead?"

(Or alternatively, if I am feeling tired that day, I will simply say that I don't know rather than engage. Because working on complex tasks with someone with "I dunno, man, it’s the job I was given" attitude is an exercise in frustration and will likely increase amount of tech debt too)

	▲	jagged-chisel a day ago \| parent [-]
		So I went back to The Business and asked "why would you even want to do that?" and the answer is that it centers on business processes that I can't reveal due to NDA. Other technical people dismissing the problem with "why would you even ..." is not productive. Many, many times, I have indeed communicated the why to those I am seeking help from and they go silent. Telling them didn't help me solve the problem. Many times, the explanation is pretty involved and people-heavy and ... not important to solving the problem. And more often than you'd think, I'm just not allowed to tell you. Now, if you think at the next level, perhaps you might suggest looking at the problem from an angle you've seen before; or that just occurred to you and hasn't yet become apparent to me. Or you happen to know an alternate product that provides something close to what I'm asking. Great, that's helpful! Attempting to diagnose my client's or employer's asinine process - I have indeed already done that and it is indeed asinine, and not up for changing - is shortsighted, just like many of the neophytes I've worked with throughout my career.

▲

abel-dev 4 days ago | parent | prev [-]

[flagged]