From mboxrd@z Thu Jan 1 00:00:00 1970 From: rendaw <7e9wc56emjakcm@s.rendaw.me> Subject: Re: guile scheme tutorial Date: Mon, 13 May 2019 16:10:34 +0900 Message-ID: <21a52ba4-140f-66f8-e886-d68aa91e5ebf@s.rendaw.me> References: <60f73aa7-e1ae-2c5d-cf47-c179a54a65ce@s.rendaw.me> <87pnoy7g1c.fsf@gnu.org> <3b95f670-336a-c7e9-b2e0-768e2bb99342@s.rendaw.me> <87ftppxgfi.fsf@gnu.org> <871s19w0ik.fsf@ambrevar.xyz> <93478463-4cdc-40dc-e27d-4f33871066df@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:43858) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <7e9wc56emjakcm@s.rendaw.me>) id 1hQ56f-0004YM-AX for help-guix@gnu.org; Mon, 13 May 2019 03:10:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <7e9wc56emjakcm@s.rendaw.me>) id 1hQ56e-0004QI-CH for help-guix@gnu.org; Mon, 13 May 2019 03:10:41 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:58113) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from <7e9wc56emjakcm@s.rendaw.me>) id 1hQ56d-0004Pg-Uj for help-guix@gnu.org; Mon, 13 May 2019 03:10:40 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0677C21B5A for ; Mon, 13 May 2019 03:10:38 -0400 (EDT) Received: from [192.168.1.35] (y236169.dynamic.ppp.asahi-net.or.jp [118.243.236.169]) by mail.messagingengine.com (Postfix) with ESMTPA id F114710378 for ; Mon, 13 May 2019 03:10:36 -0400 (EDT) In-Reply-To: <93478463-4cdc-40dc-e27d-4f33871066df@riseup.net> Content-Language: en-US List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org 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.