Commit 43b7b1d0 authored by Neil Mather's avatar Neil Mather

Update upcoming sessions

parent 8f5d1094
Pipeline #84191142 passed with stage
in 54 seconds
......@@ -277,9 +277,9 @@ free culture works available under the " ,%cc-by-sa-link " license.")
(p "(We thank the " ,(link "The Mayday Rooms" "https://www.maydayrooms.org/") " for when we met there.)")
(h3 "Upcoming sessions")
(p "Our sessions go from 18:00 till 20:00.")
(p "Tuesday 27 August 2019.")
(p "Tuesday 10 September 2019.")
(p "Tuesday 24 September 2019.")
(p "Tuesday 8 October 2019.")
(p "Tuesday 22 October 2019.")
(p "🎆 Tuesday 5 November 2019.")
)))
(define contact-page
......
<!DOCTYPE html><head><meta charset="utf-8" /><link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" /><link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png" /><link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png" /><link rel="manifest" href="/site.webmanifest" /><meta name="msapplication-TileColor" content="#da532c" /><meta name="theme-color" content="#ffffff" /><title>Come along — evalapply</title><link rel="stylesheet" href="/css/reset.css" /><link rel="stylesheet" href="/css/fonts.css" /><link rel="stylesheet" href="/css/evalapply.css" /></head><body><div class="container"><div class="nav"><ul><li><a href="/">EvalApply</a></li><li class="fade-text"> </li><li><a href="/sicp.html">SICP</a></li><li><a href="/resources.html">Resources</a></li><li><a href="/come-along.html">Come along</a></li><li><a href="/conduct.html">Code of conduct</a></li><li><a href="/contact.html">Contact</a></li></ul></div><h2>Come along</h2><p>We meet fortnightly online on IRC in the #evalapply channel on the <a href="https://webchat.freenode.net">freenode</a> server from 18:00 till 20:00.</p><p>(We thank the <a href="https://www.maydayrooms.org/">The Mayday Rooms</a> for when we met there.)</p><h3>Upcoming sessions</h3><p>Our sessions go from 18:00 till 20:00.</p><p>Tuesday 27 August 2019.</p><p>Tuesday 10 September 2019.</p><p>Tuesday 24 September 2019.</p><footer class="text-center"><p class="copyright">© 2019 EvalApply<a class="cc-button" href="https://creativecommons.org/licenses/by-sa/4.0/"><img src="https://licensebuttons.net/l/by-sa/4.0/80x15.png" /></a></p><p>The text and images on this site are
<!DOCTYPE html><head><meta charset="utf-8" /><link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" /><link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png" /><link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png" /><link rel="manifest" href="/site.webmanifest" /><meta name="msapplication-TileColor" content="#da532c" /><meta name="theme-color" content="#ffffff" /><title>Come along — evalapply</title><link rel="stylesheet" href="/css/reset.css" /><link rel="stylesheet" href="/css/fonts.css" /><link rel="stylesheet" href="/css/evalapply.css" /></head><body><div class="container"><div class="nav"><ul><li><a href="/">EvalApply</a></li><li class="fade-text"> </li><li><a href="/sicp.html">SICP</a></li><li><a href="/resources.html">Resources</a></li><li><a href="/come-along.html">Come along</a></li><li><a href="/conduct.html">Code of conduct</a></li><li><a href="/contact.html">Contact</a></li></ul></div><h2>Come along</h2><p>We meet fortnightly online on IRC in the #evalapply channel on the <a href="https://webchat.freenode.net">freenode</a> server from 18:00 till 20:00.</p><p>(We thank the <a href="https://www.maydayrooms.org/">The Mayday Rooms</a> for when we met there.)</p><h3>Upcoming sessions</h3><p>Our sessions go from 18:00 till 20:00.</p><p>Tuesday 8 October 2019.</p><p>Tuesday 22 October 2019.</p><p>🎆 Tuesday 5 November 2019.</p><footer class="text-center"><p class="copyright">© 2019 EvalApply<a class="cc-button" href="https://creativecommons.org/licenses/by-sa/4.0/"><img src="https://licensebuttons.net/l/by-sa/4.0/80x15.png" /></a></p><p>The text and images on this site are
free culture works available under the <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution Share-Alike 4.0 International</a> license.</p><p>This website (<a href="https://gitlab.com/evalapply/evalapply.gitlab.io">source</a> and <a href="/website.html">more info</a>) is built with <a href="http://haunt.dthompson.us">Haunt</a>, a static site generator written in <a href="https://gnu.org/software/guile">Guile Scheme</a>.</p></footer></div></body>
\ No newline at end of file
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><id>https://evalapply.space/feed.xml</id><subtitle>Recent Posts</subtitle><updated>2019-09-19T20:34:01+0100</updated><link href="evalapply.space/feed.xml" rel="self" /><link href="evalapply.space" /><entry><title>Adding blog posts to EvalApply</title><id>https://evalapply.space/adding-blog-posts-to-evalapply.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-08-07T20:05:00+0100</updated><link href="https://evalapply.space/adding-blog-posts-to-evalapply.html" rel="alternate" /><summary type="html">&lt;p&gt;So far, we have been making use of only the pages functionality of Haunt.
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><subtitle>Recent Posts</subtitle><updated>2019-09-24T21:55:21+0100</updated><link href="evalapply.space/feed.xml" rel="self" /><link href="evalapply.space" /><entry><title>Adding blog posts to EvalApply</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-08-07T20:05:00+0100</updated><link href="/adding-blog-posts-to-evalapply.html" rel="alternate" /><summary type="html">&lt;p&gt;So far, we have been making use of only the pages functionality of Haunt.
However, as a static site generator, it also comes with functionality for
blog posts. We've just turned this on, so we can also add in blog posts
about what we're covering in EvalApply.&lt;/p&gt;&lt;p&gt;We have already written some blog posts about our progress through SICP, so we
can backfill these posts in on the site.&lt;/p&gt;</summary></entry><entry><title>EvalApply 30th July 2019</title><id>https://evalapply.space/evalapply-30th-july-2019.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-07-30T21:18:00+0100</updated><link href="https://evalapply.space/evalapply-30th-july-2019.html" rel="alternate" /><summary type="html">&lt;p&gt;We had a fun session today, during which we decided to add to our
can backfill these posts in on the site.&lt;/p&gt;</summary></entry><entry><title>EvalApply 30th July 2019</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-07-30T21:18:00+0100</updated><link href="/evalapply-30th-july-2019.html" rel="alternate" /><summary type="html">&lt;p&gt;We had a fun session today, during which we decided to add to our
homepage a sentence about our interest in examining programming and technology
in a wider societal context. Early on we discussed that this was important to us
all, and we often end up chatting about these topics when we meet – perhaps more
......@@ -29,7 +29,7 @@ Emacs being a beautiful example of software you can see the innards of and
tinker with, should you wish to.&lt;/p&gt;&lt;p&gt;Dan did a bit of SICP.&lt;/p&gt;&lt;p&gt;Dan and Panda chatted about another French philosopher, whose name I have
unfortunately forgotten, and the philosophy of autism.&lt;/p&gt;&lt;p&gt;I read a couple of paragraphs of SICP.&lt;/p&gt;&lt;p&gt;Dan described the difference between technics and technology, which is really
interesting – a distinction between the machines themselves, and the analysis of
them.&lt;/p&gt;&lt;p&gt;&lt;img src=&quot;/images/evalapply-20190730.jpg&quot; alt=&quot;&quot; title=&quot;Eval'ing and apply'ing in the May Day Rooms&quot; /&gt;&lt;/p&gt;</summary></entry><entry><title>Read up to section 1.1.5 of SICP</title><id>https://evalapply.space/read-up-to-section-115-of-sicp.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-06T20:05:00+0100</updated><link href="https://evalapply.space/read-up-to-section-115-of-sicp.html" rel="alternate" /><summary type="html">&lt;p&gt;Read up to section 1.1.5 of SICP.&lt;/p&gt;&lt;p&gt;Some notes to self of things I found interesting:&lt;/p&gt;&lt;h2&gt;The environment&lt;/h2&gt;&lt;p&gt;I like the idea of giving more thought to the environment itself. I’ve always
them.&lt;/p&gt;&lt;p&gt;&lt;img src=&quot;/images/evalapply-20190730.jpg&quot; alt=&quot;&quot; title=&quot;Eval'ing and apply'ing in the May Day Rooms&quot; /&gt;&lt;/p&gt;</summary></entry><entry><title>Read up to section 1.1.5 of SICP</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-06T20:05:00+0100</updated><link href="/read-up-to-section-115-of-sicp.html" rel="alternate" /><summary type="html">&lt;p&gt;Read up to section 1.1.5 of SICP.&lt;/p&gt;&lt;p&gt;Some notes to self of things I found interesting:&lt;/p&gt;&lt;h2&gt;The environment&lt;/h2&gt;&lt;p&gt;I like the idea of giving more thought to the environment itself. I’ve always
thought more about the code, less about what the environment is doing.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;the interpreter must maintain some sort of memory that keeps track of the
name-object pairs. This memory is called the environment.&lt;/p&gt;&lt;/blockquote&gt;&lt;blockquote&gt;&lt;p&gt;the general notion of the environment as providing a context in which
evaluation takes place will play an important role in our understanding of
......@@ -40,7 +40,7 @@ known as tree accumulation&lt;/p&gt;&lt;/blockquote&gt;&lt;h2&gt;Special forms&l
are exceptions to general evaluation and have their own rules.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;Such exceptions to the general evaluation rule are called special forms.
define is the only example of a special form that we have seen so far, but we
will meet others shortly. Each special form has its own evaluation rule.&lt;/p&gt;&lt;/blockquote&gt;&lt;h2&gt;Applicative-order evaluation vs normal-order evaluation&lt;/h2&gt;&lt;p&gt;You can evaluate procedures in different ways.&lt;/p&gt;&lt;p&gt;I think there’s a subtle distinction beween evaluation and procedure
application that I’ve missed and need to look back over.&lt;/p&gt;&lt;hr /&gt;&lt;p&gt;That’ll do for now!&lt;/p&gt;</summary></entry><entry><title>Notes on SICP Lecture 1A</title><id>https://evalapply.space/notes-on-sicp-lecture-1a.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-03T21:42:00+0100</updated><link href="https://evalapply.space/notes-on-sicp-lecture-1a.html" rel="alternate" /><summary type="html">&lt;p&gt;Watched the &lt;a href=&quot;https://archive.org/details/halmit1a&quot;&gt;Lecture 1a video for SICP&lt;/a&gt;.
application that I’ve missed and need to look back over.&lt;/p&gt;&lt;hr /&gt;&lt;p&gt;That’ll do for now!&lt;/p&gt;</summary></entry><entry><title>Notes on SICP Lecture 1A</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-03T21:42:00+0100</updated><link href="/notes-on-sicp-lecture-1a.html" rel="alternate" /><summary type="html">&lt;p&gt;Watched the &lt;a href=&quot;https://archive.org/details/halmit1a&quot;&gt;Lecture 1a video for SICP&lt;/a&gt;.
(Not sure how exactly these correspond to the book – is it by chapter?)&lt;/p&gt;&lt;p&gt;It’s Hal Abelson giving the lectures. I find him really engaging. And, I did not
know this until I looked him up just now, but is a founding director of both
Creative Commons and the Free Software Foundation. Rad!&lt;/p&gt;&lt;p&gt;Anyway, here’s a few notes I made while watching the video.&lt;/p&gt;&lt;h2&gt;Not computers, not a science&lt;/h2&gt;&lt;p&gt;Off the bat, he calls out computer science as not really being a science. Yup. I
......
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><id>https://evalapply.space/feeds/tags/evalapply sicp.xml</id><subtitle>Tag: evalapply sicp</subtitle><updated>2019-09-19T20:34:01+0100</updated><link href="evalapply.space/feeds/tags/evalapply sicp.xml" rel="self" /><link href="evalapply.space" /><entry><title>EvalApply 30th July 2019</title><id>https://evalapply.space/evalapply-30th-july-2019.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-07-30T21:18:00+0100</updated><link href="https://evalapply.space/evalapply-30th-july-2019.html" rel="alternate" /><summary type="html">&lt;p&gt;We had a fun session today, during which we decided to add to our
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><subtitle>Tag: evalapply sicp</subtitle><updated>2019-09-24T21:55:21+0100</updated><link href="evalapply.space/feeds/tags/evalapply sicp.xml" rel="self" /><link href="evalapply.space" /><entry><title>EvalApply 30th July 2019</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-07-30T21:18:00+0100</updated><link href="/evalapply-30th-july-2019.html" rel="alternate" /><summary type="html">&lt;p&gt;We had a fun session today, during which we decided to add to our
homepage a sentence about our interest in examining programming and technology
in a wider societal context. Early on we discussed that this was important to us
all, and we often end up chatting about these topics when we meet – perhaps more
......
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><id>https://evalapply.space/feeds/tags/meta.xml</id><subtitle>Tag: meta</subtitle><updated>2019-09-19T20:34:01+0100</updated><link href="evalapply.space/feeds/tags/meta.xml" rel="self" /><link href="evalapply.space" /><entry><title>Adding blog posts to EvalApply</title><id>https://evalapply.space/adding-blog-posts-to-evalapply.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-08-07T20:05:00+0100</updated><link href="https://evalapply.space/adding-blog-posts-to-evalapply.html" rel="alternate" /><summary type="html">&lt;p&gt;So far, we have been making use of only the pages functionality of Haunt.
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><subtitle>Tag: meta</subtitle><updated>2019-09-24T21:55:21+0100</updated><link href="evalapply.space/feeds/tags/meta.xml" rel="self" /><link href="evalapply.space" /><entry><title>Adding blog posts to EvalApply</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-08-07T20:05:00+0100</updated><link href="/adding-blog-posts-to-evalapply.html" rel="alternate" /><summary type="html">&lt;p&gt;So far, we have been making use of only the pages functionality of Haunt.
However, as a static site generator, it also comes with functionality for
blog posts. We've just turned this on, so we can also add in blog posts
about what we're covering in EvalApply.&lt;/p&gt;&lt;p&gt;We have already written some blog posts about our progress through SICP, so we
......
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><id>https://evalapply.space/feeds/tags/sicp.xml</id><subtitle>Tag: sicp</subtitle><updated>2019-09-19T20:34:01+0100</updated><link href="evalapply.space/feeds/tags/sicp.xml" rel="self" /><link href="evalapply.space" /><entry><title>Read up to section 1.1.5 of SICP</title><id>https://evalapply.space/read-up-to-section-115-of-sicp.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-06T20:05:00+0100</updated><link href="https://evalapply.space/read-up-to-section-115-of-sicp.html" rel="alternate" /><summary type="html">&lt;p&gt;Read up to section 1.1.5 of SICP.&lt;/p&gt;&lt;p&gt;Some notes to self of things I found interesting:&lt;/p&gt;&lt;h2&gt;The environment&lt;/h2&gt;&lt;p&gt;I like the idea of giving more thought to the environment itself. I’ve always
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>evalapply</title><subtitle>Tag: sicp</subtitle><updated>2019-09-24T21:55:21+0100</updated><link href="evalapply.space/feeds/tags/sicp.xml" rel="self" /><link href="evalapply.space" /><entry><title>Read up to section 1.1.5 of SICP</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-06T20:05:00+0100</updated><link href="/read-up-to-section-115-of-sicp.html" rel="alternate" /><summary type="html">&lt;p&gt;Read up to section 1.1.5 of SICP.&lt;/p&gt;&lt;p&gt;Some notes to self of things I found interesting:&lt;/p&gt;&lt;h2&gt;The environment&lt;/h2&gt;&lt;p&gt;I like the idea of giving more thought to the environment itself. I’ve always
thought more about the code, less about what the environment is doing.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;the interpreter must maintain some sort of memory that keeps track of the
name-object pairs. This memory is called the environment.&lt;/p&gt;&lt;/blockquote&gt;&lt;blockquote&gt;&lt;p&gt;the general notion of the environment as providing a context in which
evaluation takes place will play an important role in our understanding of
......@@ -9,7 +9,7 @@ known as tree accumulation&lt;/p&gt;&lt;/blockquote&gt;&lt;h2&gt;Special forms&l
are exceptions to general evaluation and have their own rules.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;Such exceptions to the general evaluation rule are called special forms.
define is the only example of a special form that we have seen so far, but we
will meet others shortly. Each special form has its own evaluation rule.&lt;/p&gt;&lt;/blockquote&gt;&lt;h2&gt;Applicative-order evaluation vs normal-order evaluation&lt;/h2&gt;&lt;p&gt;You can evaluate procedures in different ways.&lt;/p&gt;&lt;p&gt;I think there’s a subtle distinction beween evaluation and procedure
application that I’ve missed and need to look back over.&lt;/p&gt;&lt;hr /&gt;&lt;p&gt;That’ll do for now!&lt;/p&gt;</summary></entry><entry><title>Notes on SICP Lecture 1A</title><id>https://evalapply.space/notes-on-sicp-lecture-1a.html</id><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-03T21:42:00+0100</updated><link href="https://evalapply.space/notes-on-sicp-lecture-1a.html" rel="alternate" /><summary type="html">&lt;p&gt;Watched the &lt;a href=&quot;https://archive.org/details/halmit1a&quot;&gt;Lecture 1a video for SICP&lt;/a&gt;.
application that I’ve missed and need to look back over.&lt;/p&gt;&lt;hr /&gt;&lt;p&gt;That’ll do for now!&lt;/p&gt;</summary></entry><entry><title>Notes on SICP Lecture 1A</title><author><name>Neil</name><email>lambda@evalapply.space</email></author><updated>2019-06-03T21:42:00+0100</updated><link href="/notes-on-sicp-lecture-1a.html" rel="alternate" /><summary type="html">&lt;p&gt;Watched the &lt;a href=&quot;https://archive.org/details/halmit1a&quot;&gt;Lecture 1a video for SICP&lt;/a&gt;.
(Not sure how exactly these correspond to the book – is it by chapter?)&lt;/p&gt;&lt;p&gt;It’s Hal Abelson giving the lectures. I find him really engaging. And, I did not
know this until I looked him up just now, but is a founding director of both
Creative Commons and the Free Software Foundation. Rad!&lt;/p&gt;&lt;p&gt;Anyway, here’s a few notes I made while watching the video.&lt;/p&gt;&lt;h2&gt;Not computers, not a science&lt;/h2&gt;&lt;p&gt;Off the bat, he calls out computer science as not really being a science. Yup. I
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment