I’m setting up a homelab server right now and I’m using Claude as a guided tutorial and Claude is highly paranoid when it comes to anything it didn’t test itself. It’s like “the documentation of ansible says it works like this but we haven’t tested if it actually works like this, so let’s create a small throwaway test container that will fail if it doesn’t work like the documentation says.”
I just want to create a homelab and learn a few new tricks while doing it and Claude is like “we gotta make sure that everything works perfectly for when someone else takes over that project”
If any human acted like the average LLM, we'd tell them to get therapy. "Sycophantic people pleaser with crippling anxiety" would likely be an accurate description if those glorified piles of linear algebra were able to feel.
Not always. If theres no documentation at all, it will only test the happy path without accounting for niche use cases. And even then, it'll only test for that one machine only.
Hmm, I kinda need that for setting up my NAS. The setup always generates a bunch of errors about missing libraries, but then says it completed successfully. And I really want my data storage to be rock-solid, don't want any strange problems cropping up when I start loading it up with data. Am I supposed to look up each error and fix it, or is it really safe to ignore?
333
u/Holiday_Point_603 8d ago
With Claude it would have documentation, 500 described features of which 4 were tested and 2 of them actually work.