Learning syllabus ideas

[colinleach]

Finding exercises to go with the concepts can be hard. I've tried to list some preliminary suggestions below, for an incomplete list of likely concepts. Track names in parentheses mention this exercise in the config.json (I haven't checked if they have all published it on a syllabus).

Concept	Some possible exercises
basics (merged)	lasagna (merged)
booleans (merged)	annalyns-infiltration (merged)
numbers (PR #711)	cars-assemble (PR#713)
conditionals (merged)	vehicle-purchase? (C++, Go, JS, jq, Swift) cars-assemble? (Clojure, C#, F#, Go, Java, Lua, Julia)
lists (wip)	making-the-grade? (C++, Python) bird-watcher? (Clojure, C#, F#, Go, Java, JS, Julia)
arrays	making-the-grade? (C++, Python) bird-watcher? (Clojure, C#, F#, Go, Java, JS, Julia)
strings (PR #712)	log-levels? (C++, Elixir, Clojure, CLisp, C#, F#, Gleam, Java, Python, Julia)
bit-operations (PR #716)	secrets? (Crystal, Elixir, Gleam, Java, Julia)
chars (PR #715)	squeaky-clean? (Clojure, C#, F#, Elm, Java, Julia)
ranges (PR #718)	chessboard/chess-game? (Crystal, Ruby, Elixir, Go, Julia)
when (wip)	guessing-game? (Elixir, F#, Gleam)
nullability (PR #714)	tim-from-marketing? (C#, Java)
sets	gotta-snatch-em-all? (Elm, Gleam, Java)
maps	international-calling-connoisseur? (Clojure, C#) inventory-management? (Python, Julia)
pairs-and-triples	???
randomness (wip)	captains-log? (Elixir, Java, JS, Julia) maze-maker? (Elm) roll-the-die? (C#) animal-magic? (Go)
enums	boutique-inventory? (Elixir, Gleam, Ruby) logs-logs-logs? (C#, Go, Java)
recursion	bird-count? (Elixir, Gleam) dna-encoding? (Elixir) pizza-order/pizza-pricing? (JS, F#, Gleam)
functions	???
loops	interest-is-interesting? (C++, Clojure, Crystal, C#, F#, Go) mixed-juices? (JS, Julia)
higher-order-functions	coordinate-transformation? (JS)
classes	jedliks-toy-car/elons-toys? (Java, C#, Go)
exceptions	calculator-conundrum? (C#, Java) factory-sensors? (JS, Julia)
types	???

A syllabus has only one concept exercise per concept. Where there are multiple exercise suggestions in a cell, that means making a choice.

[SleeplessByte]

Arrays is actually not bird-watcher in JS. In JS we separated:

• arrays (Elyses Enchantments)
• for-loops, increment-and-decrement (Bird Watcher)
• while-loops, switch-statements (Mixed Juices)
• callbacks (Fruit Picker)
• array-loops (Elyses Looping Enchantments)
• array-analysis (Elyses Analytic Enchantments); you need callbacks to use this
• array-transformations (Elyses Transformative Enchantments); you need callbacks
• array-destructuring, object-destructuring (Elyses Destructured Enchantments); this is shape matching an array / object
• rest-and-spread (Train Driver); this is rest slicing/parameters

It's all array / list related, but splitting them may make sense for Kotlin too because it allows us to cover more StdLib without overwhelming students (and we already have the exercises!)

[colinleach]

splitting them may make sense for Kotlin too

Thanks for the clarification. I already drafted Lists, haven't started Arrays yet, but I always expected they'd be separate. The table above is mainly a "stuff to think about later" list!

[SleeplessByte]

(JS arrays are actually lists so yeah)