Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

WIP for Event 2017 06 03 #6

Open
wants to merge 67 commits into
base: gh-pages
Choose a base branch
from
Open

WIP for Event 2017 06 03 #6

wants to merge 67 commits into from

Conversation

firthh
Copy link
Collaborator

@firthh firthh commented May 8, 2017

Opening this for visibility of the changes that are getting made to remove Quil and the turtles. The Berlin fork of the curriculum has been chosen as work has already been done to start to remove them.

Sections that still contain Turtles or Quil:

  • "Introduction" section - Exercise 2 requires Quil to draw some lines
  • "Your First Program: Drawing Lines" section - uses Quil entirely
  • "[bonus module] Sequences" section - still uses Turtles and Quil

Jelle Akkerman and others added 30 commits January 17, 2016 14:13
The data validation example is a bit tricky to read.

This commit begins with an example simpler followed immediately with the
generalisation.

The validation case is then presented (with comments added).

The greater than/ less than examples are now removed as they don't add
much.
Spells out the situation with nested `if`s to better demonstrate why
`cond` is useful.

Would be better with an example that needs yet more control paths (to
demonstrate scalability of `cond`).
These examples are more self-explanatory and don't require the learner
to know about `partial` and how `name` operates on keywords.
Simplification of the `if` examples
This follows the same pattern used to introduce `if`: start with an
example and explanation, show the general form, then show a more
elaborate example.
…ledge

Explain map/ reduce with less foreknowledge
This overlays a link onto the logo in the bottom left, so you can easily
jump back to the overview.
Add a button to go back to the overview
There's some differences to how we interact with the different REPLs, so
I've tried to cover both. Perhaps some parts can be rewr
Also got the Nightcode shortcuts wrong for eval'ing first time.
Instead of having a `pygments` key in the config yaml, you're now
supposed to use `highlighter`.
Turns out GH pages doesn't like the new syntax

This reverts commit 037b0c7.
Spells out the situation with nested `if`s to better demonstrate why
`cond` is useful.

Would be better with an example that needs yet more control paths (to
demonstrate scalability of `cond`).
This follows the same pattern used to introduce `if`: start with an
example and explanation, show the general form, then show a more
elaborate example.
Get rid of the turtle references, and instead use self-contained, simple
examples and exercises.
- removed references to turtle functions
- reintroduced total-bill etc instead
- explain predicate functions (not just about names)
- explain anonymous functions as useful predicates
- explain side-effects (to those that get this far)
Split the overview into two slides, the first section is the basic
curriculum, the second is a choice of applications to try out, beginning
with Quil.
Robsteranium and others added 25 commits June 10, 2016 16:03
Introduce functions with a simpler example
Plus minor edits to resolve merge conflict
Use update instead of update-in -- less syntax.
Saves a few steps of explaination when introducing this.
With the current version of Nightcode the instructions for the basic REPL usage don't work anymore.

For the example to work, the entire `(defn draw ...` form needs to be selected and the keyboard shortcut is also different.
* Numbers are already a well known concept to non-programmers.
  Writing them down is just natural.
* That makes numbers the easiest type to grasp.
* It also allows for infix notation and some first experiments on the REPL.

(Of course this is opinionated.)
Fix Nightcode instructions for "Eval Selection"
Put docstring after function name in `defn` intro
@practicalli-johnny
Copy link
Member

@firthh are you able to resolve the conflict & merge this pull request into the curriculum? Or would you like some help?

We have a volunteer training event on the 23rd May. It would be great if people had some time to review the curriculum changes before then.

Thank you

@firthh
Copy link
Collaborator Author

firthh commented May 15, 2017

@jr0cket I'll have a go at resolving the conflicts so that it's can be merged. But if it can't I also created a new branch that's currently even with the gh-pages branch - https://github.com/ClojureBridgeLondon/curriculum/tree/event-2016-09-30
So if there is any need of a force push there's still history

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.