Just once in my life I would like to start learning a new tool and encounter structured documentation written to help a new user learn how it works, rather than a disorganised assortment of random thoughts the developer had while writing the code
@djnavarro you’re going to end up writing it (for no $ or thanks), aren’t you?
@djnavarro and that is exactly why publishing such texts ought to count in research evaluation, as i argue here: https://psyarxiv.com/kju82/
@djnavarro this is why I advocate [1] "lesson-driven development" - write the tutorial first, *then* write the software that makes the tutorial do-able.
[1] by "advocate", of course, I mean "shout hopelessly into the uncaring void"
@djnavarro this is always the missing piece that makes learning frustrating.
@jsonbecker @djnavarro I read the last word as "fascinating", and then realized that reading here while still dopey from a nap is not necessarily a good idea.
@djnavarro this seems to be generally true, but I have to say that the Quarto documentation is the best I have ever seen: well-structured and clearly laid out.