From: Viet Le <vietlq85@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Help with Learning Programming and LISP
Date: Wed, 11 Sep 2019 23:15:45 +0100 [thread overview]
Message-ID: <CAG_8+G6+x3AHnyGo9dA5+hRbHYawtGyxjR20g5WQkqTEY3zXPw@mail.gmail.com> (raw)
In-Reply-To: <ffa86414-1668-d227-f06e-8b44552e3043@posteo.de>
Thank you Zelphir, this looks great!
Viet
On Wed, 11 Sep 2019 at 22:24, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
wrote:
> There is at least one SRFI for a unit test library. Is that sufficient as
> "support for TDD"?
>
> https://srfi.schemers.org/srfi-64/srfi-64.html
>
>
> On 9/11/19 10:53 PM, Viet Le wrote:
>
> Thanks for your recommendation. May I ask if Scheme has support for TDD or
> are there any TDD libraries/frameworks in Scheme? A quick online search
> didn’t show desired results. I found only TDD for Clojure.
>
> Thanks,
> Viet
>
> On Tue, 10 Sep 2019 at 22:24, Zelphir Kaltstahl <
> zelphirkaltstahl@posteo.de> wrote:
>
>> I would like to add "The Little Schemer" to the list of good books
>> suggested here. Damn did I get a lot out of that little book. It starts
>> at the very beginning, but accelerates quickly.
>>
>> I would say I got more out of SICP than The Little Schemer, but both are
>> phenomenal books in my opinion. SICP has many many pages and covers many
>> topics. More than are treated in The Little Schemer, but the content in
>> The Little Schemer is very enlightening as well, just like many things
>> in SICP were for me. In The Little Schemer I read multiple chapters
>> multiple times to get a better understanding and often was rewarded by
>> understanding it better and even better, when I later typed that code
>> into my machine and wrote comments for everything. I am far from
>> finished with SICP, but I had a lot of "Aha!" moments with it too. Both
>> highly recommended books, but they might take also some time to get
>> through, if you have a job and not much time to spend on the books.
>>
>> Haven't read Practical Common Lisp.
>>
>> Realm of Racket was a little disappointing for me personally, as in my
>> version there was some code missing and thus some example did not work
>> (the procedure `decay` is missing in my book). I also did not buy in to
>> the "Big bang" thingy that much. I would have preferred to write
>> something on top of a minimalistic 2D engine instead. In general is it a
>> nice idea though, to get content across by writing small games.
>>
>> I still have PAIP (Paradigms of Artificial Intelligence Programming)
>> here and am not sure how to sort it in. So far it has been good content,
>> but I also have not progressed very far into it yet. I am rewriting the
>> code in Scheme so far, when I try out the code of it.
>>
>>
>> --
> Kind regards,
> Viet
>
> --
Kind regards,
Viet
next prev parent reply other threads:[~2019-09-11 22:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.370.1568090751.2189.help-guix@gnu.org>
2019-09-10 20:31 ` Help with Learning Programming and LISP Zelphir Kaltstahl
2019-09-11 20:53 ` Viet Le
2019-09-11 21:24 ` Zelphir Kaltstahl
2019-09-11 22:15 ` Viet Le [this message]
2019-09-09 16:18 Raghav Gururajan
2019-09-09 16:38 ` John Soo
2019-09-09 17:04 ` Raghav Gururajan
2019-09-09 17:20 ` Jesse Gibbons
2019-09-09 16:50 ` Tobias Geerinckx-Rice
2019-09-09 16:53 ` Tobias Geerinckx-Rice
2019-09-09 17:05 ` John Soo
2019-09-09 17:04 ` Raghav Gururajan
2019-09-09 17:20 ` Pierre Neidhardt
2019-09-09 17:18 ` Vladimir Sedach
2019-09-09 20:11 ` Ricardo Wurmus
2019-09-12 1:16 ` Raghav Gururajan
2019-09-12 6:34 ` Konrad Hinsen
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG_8+G6+x3AHnyGo9dA5+hRbHYawtGyxjR20g5WQkqTEY3zXPw@mail.gmail.com \
--to=vietlq85@gmail.com \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).