From: randomlooser <randomlooser@riseup.net>
To: guile-user@gnu.org
Subject: vlog about Guile
Date: Thu, 12 Nov 2020 10:37:36 +0100 [thread overview]
Message-ID: <01fa69744cee41e30d0f90961018d30d84213585.camel@riseup.net> (raw)
Hello
I'm Catonano, from a brand new email address
I'm trying to diminish the role of Google in my life, gradually
I made a couple of videos about Guile
They are an experiment
In the videos I explain, in my own terms, how to read a line delimited
file in Guile scheme
Here they are
https://peertube.social/videos/watch/playlist/03ebdbfb-7285-4d1f-8787-01de111a6d6d
It's not a groudbreaking use case
My assumption is that the person(s) watching these videos may be a
beginner, not only in scheme or Guile, but in programming in general
In fact, I go through what I think is the discovery process in
painstaking detail and slowliness
I was inspired by this talk
https://archive.fosdem.org/2017/schedule/event/legacy_docs/
and this blog post
https://www.hillelwayne.com/post/learning-a-language/
I mention both in the introduction
In the past I hinted at how I feel that the Guile documentation is
lacking in some regards
So I made these videos as an experiment
In the future I could try to cover more use cases
Some remarks:
It's not written material, it's video
This alone is a stark departure from the usual style of materials
discussing Guile
It's not feature oriented, it's use case oriented
I introduce open-input-file, read-line and with-input-from-file as the
need arises, not based on where they are in the manual
It's incomplete and maybe even incorrect in some aspects
But it strives to provide the watcher with a bit of immediate reward
This is another striking departure from the usual
I understand that to many people here, the case of reding a file in
painstaking detail and slowness is not exactly fun
You need to put yourself in someone else's shoes to watch this
Anyway, i thought it was useful to mention this here
Thanks
next reply other threads:[~2020-11-12 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 9:37 randomlooser [this message]
2020-11-13 23:48 ` vlog about Guile Thien-Thi Nguyen
2020-11-14 7:39 ` randomlooser
2020-12-28 0:52 ` Joshua Branson via General Guile related discussions
2020-12-28 5:54 ` Zelphir Kaltstahl
2020-12-29 3:17 ` Joshua Branson
2020-12-29 8:14 ` Zelphir Kaltstahl
2020-12-29 14:23 ` Amin Bandali
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01fa69744cee41e30d0f90961018d30d84213585.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=guile-user@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).