I completely agree with you. This was the main thing slowing me down when I started to learn Clojure last year. I'm now learning Emacs and and Elisp and I fin

I completely agree with you. This was the main thing slowing me down when I started to learn Clojure last year. I'm now learning Emacs and and Elisp and I find the documentation even more difficult to comprehend somehow. Two examples: Literate programming with org-babel: almost none of the documentation that I can find shows "real" examples with multiple header properties or variables being set for an org-babel file. I don't know how to mix and match them. The docs tend to show the most minimal example and I've been spinning my wheels for days trying to figure out how to integrate into my workflow. Another elisp example: using auth-sources.el for handling credentials. I'm trying to enhance a few major modes to add support for storing server credentials, and none of the examples show how to actually prompt a user for a username and password to save it for later in the secure key store. I've checked other projects, and people do it in different ways, and they all seem needlessly complicated, with core auth logic embedded directly in unrelated function calls. Compare this: https://www.gnu.org/software/emacs/manual/html_mono/auth.html https://www.gnu.org/software/emacs/manual/html_mono/auth.htm... To this: https://pypi.org/project/keyring/ https://pypi.org/project/keyring/ Edit: I'd like to add, I am loving Emacs and Clojure. I think it's worth the slog, but there is room for improvement for making a lot of these systems more approachable to the complete newcomers.