unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Blake Shaw <blake@nonconstructivism.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: guile-user@gnu.org
Subject: Re: SD4F: (exist? procedure-**maximum**-arity)
Date: Wed, 29 Dec 2021 18:47:54 +0700	[thread overview]
Message-ID: <87czlfws2d.fsf@nonconstructivism.com> (raw)

Olivier Dion <olivier.dion@polymtl.ca> writes:

> Out of topic here, but what's your first impression of the book?  I was
> thinking of asking it for my birthday :-)

As someone whose introduction to scheme was sicp about a year ago, which
I spent about three months with only moving forward after solving each 
problem, getting my ass kicked every few sets of exercises (some taking
a week!) until I decided to just do a cursory overview of the rest of
the material from Chapter 4 onwards, so far SD4F has been fantastic.

So far it's a lot of the same ideas from sicp, but instead of traversing the
entire gamut of programming it's focused on one objective: explaining
how to write the most generic, composable, maintainable and reusable
software possible. So in a sense, it feels like a "refined, abbreviated,
applied sicp follow-up".

Not to say SICP isn't geared towards application of ideas, because it
absolutely is, but the first exercises don't, for example, ask that you
prove Ackermann's function. So far it sticks to the practical aspect of
software design, and has been easy to follow. As someone new to scheme
it seems like the first text I've encountered that doesn't only teach
scheme but teaches how to design software in scheme. Highly recommended!

-- 
“In girum imus nocte et consumimur igni”



             reply	other threads:[~2021-12-29 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 11:47 Blake Shaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-29  1:23 SD4F: (exist? procedure-**maximum**-arity) Blake Shaw
2021-12-29  4:04 ` Olivier Dion via General Guile related discussions
2021-12-29 12:49 ` Zelphir Kaltstahl

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=87czlfws2d.fsf@nonconstructivism.com \
    --to=blake@nonconstructivism.com \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).