| Pronouns | they/them |
| Personal website | https://michd.me |
| Github | https://github.com/michd |
| Pronouns | they/them |
| Personal website | https://michd.me |
| Github | https://github.com/michd |
My biggest problem with the concept of LLMs, even if they weren’t a giant plagiarism laundering machine and disaster for the environment, is that they introduce so much unpredictability into computing. I became a professional computer toucher because they do exactly what you tell them to. Not always what you wanted, but exactly what you asked for.
LLMs turn that upside down. They turn a very autistic do-what-you-say, say-what-you-mean commmunication style with the machine into a neurotypical conversation talking around the issue, but never directly addressing the substance of problem.
In any conversation I have with a person, I’m modeling their understanding of the topic at hand, trying to tailor my communication style to their needs. The same applies to programming languages and frameworks. If you work with a language the way its author intended it goes a lot easier.
But LLMs don’t have an understanding of the conversation. There is no intent. It’s just a mostly-likely-next-word generator on steroids. You’re trying to give directions to a lossily compressed copy of the entire works of human writing. There is no mind to model, and no predictability to the output.
If I wanted to spend my time communicating in a superficial, neurotypical style my autistic ass certainly wouldn’t have gone into computering. LLMs are the final act of the finance bros and capitalists wrestling modern technology away from the technically literate proletariat who built it.
Similar voice mail today. Replied via their messaging platform and asked for acknowledgment. Acknowledged, and THEN they mention it is something that needs confirmation over the phone. After 2 back and forths. The second voice mail didn't even mention this.
I called up and went through the identity verification stuff and then finally reiterated "yes I am okay with <question>".
Like if something absolutely requires to be over the phone
1) Stop that
2) State it immediately
The best advice I have for new nerds: Refuse to pay rent.
Don't subscribe. Don't lease. Don't use their cloud. Don't slip down the freemium slope. Don't create accounts on their services.
Buy it once. Run it local. Avoid commercial software.
It'll be a huge pain and you'll be an outsider but it'll be endless, interesting, and hard fun that'll pay you back with a curious mind and an understanding of the fabric of our intellectual infrastructure that will make you light-years more capable, useful, and healthy than the "AI" zombies.
Okay so `scanimage` has a `--device-name` parameter I can use. `scanimage --list-devices` first dumps the same HTML and then, indeed, lists two devices. One connected via USB, and one on the network.
Given that the HTML just appears in unrelated command output I'm not super confident that specifying the device will actually prevent the problem but let's find out.
So, what gives? What changed?
Well. Also last week, I bought a brother inkjet printer; much newer. This sits in a different room and connects to the wifi, but isn't otherwise connected to a computer, let alone the server I mentioned.
And sure enough, when I unplug this new printer, `scanimage` works properly.