| ▲ | CoolGuySteve 8 hours ago | ||||||||||||||||
"give them difficult tasks beyond your own intellect?" Lol no, I've yet to find a model with those properties. Sounds like a fast track to AI psychosis. The domain I work in doesn't have enough public documentation for these models to be particularly helpful without a lot of handholding though. | |||||||||||||||||
| ▲ | hombre_fatal 8 hours ago | parent [-] | ||||||||||||||||
I've been working on a luks+btrfs+systemd tool (for managing an encrypted raid1 pool). While I have worked with each individually, it's not obvious what kind of cases you have to handle when composing them together. A lot of it is simply emergent, and the status quo has been to do your best and then see what actually happens at runtime. Documentation is helpful to describe high-level intentions, but the beauty is when you have access to source code. Now a good model can derive behavior from implementation instead of docs which are inherently limited. I implemented the luks+btrfs part by hand a few years ago, and I resurrected the project a couple months ago. Using source code for local reference, Claude discovered so many major cases I missed, especially in the unhappy-path scenarios. Even in my own hand-written tests. And it helped me set up an amazing NixOS VM test system include reproduction tests on the libraries to see what they do in weird undocumented cases. So I think "tasks beyond our intellect (and/or time and energy)" can be fitting. Otherwise I'd only be capable of polishing this project if luks+btfs+systemd were specifically my day job. I just can't fit so much in my head and working memory. | |||||||||||||||||
| |||||||||||||||||