2,293 karma · joined September 25, 2016
A more innocent time tbh
I've had the same "problem" and feel like this is the major hazard involved. It is tricky to validate the written work Claude (or any other LLM) produces due to high levels of verbosity, and the temptation to say "well, it works!"
As ever though, it is impressive what we can do with these things.
If I were Simon, I might have asked Claude (as a follow up) to create a minimal ansible playbook, or something of that nature. That might also be more concise and readable than the notes!
That said, I have no doubt there are also bots setting out to generate FOMO
Long term, I wonder if we're exiting the "platform compute" era, for want of a better term. By that I mean compute which can run more or less any operating system, software, etc. If everyone is siloed into their own vertically integrated hardware+operating system stack, the results will be awful for free software.
In the meantime, I guess it is time to return to degoogled Android, for me at least.
Another good example of Google's worst instincts, though: backups. The backup API can only be implemented by things which are included at build time, so apart from e/OS/ I've never seen an option except Drive. (e/OS/ supports nextcloud as a target)
That is a little unfair: this is the language of economics rather than physics, so if you are paying for 100w and getting 300w, that is indeed over 100% efficient. SCOP is a more "correct" term but is less clear when communicating with the public and (IMO) is mostly for professionals or people with a technical understanding of heat pumps. Nobody thinks they defy the laws of physics though.
If you blat your password with generate, it can be recovered because it is in git. A nice to have for pass might be a flag to autoinsert only on the first line, but in lieu of that, pwgen should do the job and is what pass uses under the hood.
On that note, I strongly recommend qwen3:4b. It is _bonkers_ how good it is, especially considering how relatively tiny it is.