Pierre Neidhardt <m...@ambrevar.xyz> writes:
> A well written manual might not be the only answer we are looking for. How > do we teach complex concepts in schools? With examples and exercises. > Maybe we should do that. Blog articles could be a good fit. I’m not a fan of blog posts for teaching, because they quickly lose relevance. An example: recently someone on IRC said they were following your packaging tutorial and something wasn’t working; someone else then said that the blog post was outdated. I don’t recall the details, but I find this worrying, because people might spend time learning something from blog posts only to have to unlearn things again. Blog posts are great for outreach and to spawn contemporary discussions. But I think that ultimately we should enhance the manual. We are not limited to having just one document that needs to meet all requirements. We can have more than one thing. Previously, we floated the idea of having a Guix cookbook with short tutorials showing how to achieve well-defined tasks such as writing a package (i.e. an updated and distilled version of your blog post perhaps), setting up a bluetooth-enabled MPD-powered media workstation, configuring a complex web application with database, web server, etc. I’d really like to see such a cookbook become part of Guix. It would always be up-to-date and it can provide much needed examples that might otherwise clutter up the manual. What do you think? Shall we start with converting your packaging tutorial? -- Ricardo
