all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: rendaw <7e9wc56emjakcm@s.rendaw.me>
To: help-guix@gnu.org
Subject: Re: guile scheme tutorial
Date: Mon, 13 May 2019 16:10:34 +0900	[thread overview]
Message-ID: <21a52ba4-140f-66f8-e886-d68aa91e5ebf@s.rendaw.me> (raw)
In-Reply-To: <93478463-4cdc-40dc-e27d-4f33871066df@riseup.net>


On 5/9/19 1:35 AM, swedebugia wrote:
> On 2019-05-08 15:15, Pierre Neidhardt wrote:
>> For what it's worth, most of rendaw's comments resonate to me, from back
>> when I first got started with Guix.
>>
>> But now, with hindsight, it's not obvious to me anymore what can be
>> fixed in the manual.
>>
>> I believe the reason for this is simply that Guix and all its
>> concepts are a lot to take for newcomers, it's simply too hard to digest
>> even after multiple readings.  It takes time and practice.
>>
>> 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.
> +1
>
I'm definitely behind the examples thing.  My guide has some (ex:
disabling root login) but it's not the first place you'd go looking for
that.  I'm not sure I like blogs though - IMO those are good for topical
writing, like release announcements, admin changes, postmortems, etc,
but I'd never go there if I had a specific technical question and by
nature they're not organized for such use.

What about a wiki like what Arch does?  I know nothing about wiki
administration, but the Arch wiki is full of basic (non-concept
information - how to install and configure package x or y) and specific
examples with snippets (how to enable a microphone in alsa).

Also if we're talking about 3rd party blogs TBH I think they're fairly
hard to find.  Having an official curated list of 3rd party
documentation would be great, but nothing beats official documentation
for discoverability.

  reply	other threads:[~2019-05-13  7:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 12:45 guile scheme tutorial amirouche
2019-05-03 17:15 ` Guy fleury
2019-05-03 21:11 ` Laura Lazzati
2019-05-03 23:44 ` amirouche
2019-05-04  1:51 ` rendaw
2019-05-04  6:08 ` rendaw
2019-05-04  8:57   ` Ludovic Courtès
2019-05-07  4:35     ` rendaw
2019-05-08 12:46       ` Ludovic Courtès
2019-05-08 13:15         ` Pierre Neidhardt
2019-05-08 16:35           ` swedebugia
2019-05-13  7:10             ` rendaw [this message]
2019-05-13  8:00               ` Pierre Neidhardt
2019-05-08 20:21           ` Guix cookbook (was: guile scheme tutorial) Ricardo Wurmus
2019-05-09 15:14             ` Pierre Neidhardt
2019-05-09 21:38               ` Ricardo Wurmus
2019-05-13  9:08                 ` Guix cookbook swedebugia
2019-05-04 11:02   ` guile scheme tutorial amirouche
2019-05-04 11:25     ` Laura Lazzati
2019-05-07  2:15     ` rendaw
2019-05-07  7:09       ` amirouche
2019-06-06 15:45 ` Laura Lazzati

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21a52ba4-140f-66f8-e886-d68aa91e5ebf@s.rendaw.me \
    --to=7e9wc56emjakcm@s.rendaw.me \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.