Just two replies to two remarks
How do you write documentation for someone who is unquestionably talented with tech but never spends even one full minute on any single document while trying to learn something new?
Ideally I feel that documentation should be more use-case based or at least provide good use-case examples for everything. Understanding user-stories might be an idea here.
Also I’ve come to realize that the flake vs non-flake divide appears to have a fairly negative impact on all of this onboarding experience. The communication around this feature is plainly contradictory. Some people recommend it in spite of being experimental, others do exactly the opposite because it is experimental.
You can see how George gets lost in that part of the jungle.
The beginner experience is so horrible with the unofficial docs everywhere
Again, I feel the how to get anything done question should be the focus. Where anything can be really anything.
Note what George says at some point: “I am interested in being able to use Nix to quickly deploy cloud instances.”
So wouldn’t it be great if we had documentation for that use case?