Yesterday a student came to me with project questions. She was trying to learn some ground-level tool basics (how useState works in React, but details don’t matter), and she was just hopelessly confused: the pieces were there, fragments of nascent understanding littered all around, but somehow it just wasn’t coming together for her.
She walked me through her fragments of non-working code, and as I was trying to figure out how she’d got so lost, she popped back to her documentation source:
@inthehands I wonder if the concept of documentation fades away
I realized I tend to avoid software that forces me to study the concepts and the philosophy of it first from the documentation (For example, #Lilypond didn't let me to go quickly into writing things there).
Watching some junior devs at work - they rely exclusively on prompts given by the IDE, giving at most one-line descriptions of function arguments.
When that fails, they refer to library source code, never the documentation
Currently I'm setting up an environment to create a new song book. I'm using #lilypond, #latex, #git, and #jenkins.
My kid(12) wants to help creating the book. Now I'm in trouble: should I teach him #vim (no, #emacs isn't a choice!), or should I be easy on his soul and the rest of his life by teaching him some gui text editor?
@choanmusic the details are at the start of that thread, but basically it started when using #org2blog to post to #wordpress, #lilypond examples compiled to png, but uploaded the full page, not the cropped. Using dev orgmode solved this… but broke #orgroam