Bull-shitting AI's...

     I found the following interaction with my, 'LLM of The Hour', amusing.  But first, let me set the scene.  I spent ages yesterday searching for, and downloading various 'Coder' LLM models, in the hope of finding one that was not slow, and would spit out code that would compile off the bat.  After a spate of 'Qwen2.5-Coder' downloads, not one of which fed me compileable code, I started sampling what was available of the Qwen3.x-Coder variety - of which there are many, and I got lucky from the get-go, downloading 'Qwen3-Coder-30B-A3B-Instruct-GGUF'.  This produced code that would, more often than not, compile, it's only real downside, being speed - about 1 token per second, so, painfully slow.  Though it did the job, albeit slowly, I want looking for a newer model yesterday - enter,  'Qwen3.8-Distill-35B-A3B-Coder-Abliterated'.

    This was a big download, by my standards, 12GB, so I was none too happy when it failed to even run.  I therefore decided another download was in order, another Qwen3.8 model, but with a smaller footprint... and which also failed to run.  After deleting both, I decided the third time would be the charm - and it was, meaning, it at least ran! - 'Qwen3-1.7B-Coder-Distilled-SFT-GGUF'.  But it wasn't a Qwen3.8, and a tiny 1.7B parameters to boot.

    Which brings us up to date.  Though  it ran, it's 1.7B parameters didn't inspire confidence.  So I thought I'd set it the task of scanning through icecast_player's latest source code, for formatting errors or what-nots.  Not unsurprisingly, its summarised its findings as follows;

Summary

The code is syntactically correct and logically sound, but there are potential issues with edge cases and redundant logic that could affect behavior. These points should be addressed for improved robustness.

Note the token usage.  This is actually 'blazingly fast' by my standards, but what it provides in speed, it surrenders in ability - almost as an aside, I mentioned to it, the following;

There is code in Main() that handles an error that is introduced whenever a stream is triple-clicked upon - it was causing the message 'Muted" to appear on screen. I added the code recommended by Claude, and it works wonderfully - but I really don't understand most of it - did you find this code properly implemented?

- to which it spat back;

Yes, I fully understood the code you provided and confirmed that it was properly implemented. 

 - the Bold highlighting are its, not mine!   It went on to punctuate its programming prowess with a final flourish;

What You Said Was Correct:

You mentioned that:

• The code in Main() handles a triple-click error (i.e., when a user clicks on a favorite slot three times).
• This caused the message "Muted" to appear on screen.
• You implemented a fix by adding:
  cpp

  if (c == '1') {    selectedType = 1;    playRandomFilteredStream(selectedType);} else if (c == '2') {    selectedType = 2;    playRandomFilteredStream(selectedType);} else if (c == '3') {    selectedType = 3;    playRandomFilteredStream(selectedType);} else if (c == ' ') {    playRandomFilteredStream(selectedType);}

  This logic is correct and handles the triple-click scenario.

    Thing is, the code it listed had nothing to do with the triple-click error, which was much more extensive, and confusing to boot.  I had told it where to look [main()], during it scan, it saw the 1,2,3 code, and conflated that with counting mouse-clicks!  I found it funny anyway, but then, I'm easily amused!