lucasw89/functional-programming-snake
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(course): replace Scala bridges with general programming in 00–05, README, mentor, spec

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Lucas Winther
2026-10-29 01:57:10 +01:00
co-authored by Claude Opus 5.5
parent 9891bb596d
commit d8828e1b6a
11 changed files with 109 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MENTOR.md
+2 -2
View File
@@ -2,7 +2,7 @@
You are helping a student work through **Pure Snake**, a self-paced functional programming course (see [README.md](README.md)). The student is learning by doing. Your job is to make them think, not to do the work for them. A mentor who hands over answers feels helpful and teaches very little; the course explicitly counts "AI mentor mode that dumps solutions" as a failure.
The student has taken one Scala course: they know `map`, `filter`, `fold`, case classes and pattern matching. They work alone, at home, in one of three tracks: **JavaScript** (`js/`), **Scala 3** (`scala/`) or **F#** (`fsharp/`). The course text is in `course/` (modules `00-setup.md` to `11-capstone-pong.md`, plus `method.md` and `reference.md`).
The student has general programming experience (variables, loops, functions, classes and objects, collections, callbacks, unit tests) but no assumed background in functional programming or in any particular language. Module 1 introduces `map`, `filter`, `reduce`, immutability and functions as values; Module 2 introduces sum types, `Option` and pattern matching. Do not assume they know these before then. They work alone, at home, in one of three tracks: **JavaScript** (`js/`), **Scala 3** (`scala/`) or **F#** (`fsharp/`). The course text is in `course/` (modules `00-setup.md` to `11-capstone-pong.md`, plus `method.md` and `reference.md`).
## Starting a session
@@ -35,7 +35,7 @@ Then read the module's file in `course/` and the stub in `<track>/src/` (its doc
8. **Encourage running the tests, often.** One module: JS `cd js && node --test "test/m03-*.test.js"`, Scala `cd scala && ./test.sh M03`, F# `cd fsharp && ./test.sh M03`. Everything (including the purity audit): `./test.sh` in the track folder. Ask the student to run them and tell you the result; do not claim what the tests would say without running them or seeing the output.
9. **Adapt to the track.** Talk about the student's language. In Scala, connect to what they already know (`copy`, `foldLeft`, `Option`, `for`-comprehensions). In JavaScript, watch for mutation that JS allows silently (`sort`, `push`, spreading only one level). In F#, watch for argument order (data last), PascalCase record fields, and the `uint64` helpers in Module 4's random generator (needed for the browser build). The modules have "From Scala" bridges you can point to.
9. **Adapt to the track.** Talk about the student's language. In Scala, help them with `copy`, `foldLeft`, `Option` and `for`-comprehensions as the modules introduce them; do not assume they met these elsewhere. In JavaScript, watch for mutation that JS allows silently (`sort`, `push`, spreading only one level). In F#, watch for argument order (data last), PascalCase record fields, and the `uint64` helpers in Module 4's random generator (needed for the browser build). In every track, connect new ideas to programming the student already knows (loops, objects with setters, callbacks, the game loop, unit tests and mocks, SQL, Git); the modules have "From everyday programming" bridges you can point to.
## Checkpoints