Polygon-first curriculum
- Dominant language
- Haskell
- Stars
- 1.3k
- Forks
- 201
- PR merge metrics
- No merged PRs in 30d
Description
Another idea that came up in conversation with @alphalambda and LSU's people.
Currently, we introduce things in effectively this order:
1. Rectangles and circles and text
2. Transformations, especially translation.
3. Top-down design
4. Polygons, arcs, and sectors
Instead, they are starting with polygons and the coordinate plane, and then introducing other shapes and transformations. The advantage is that it gives students something concrete and numerical to think about, as opposed to the very abstract idea of a picture. When students study translation, they can see how it actually changes the coordinates of each vertex of the polygon, and then build their understanding of how it operates on the whole shape on that foundation. It also delays the need to introduce transformations, which are their own sticking point for students.
I'm not at all clear on how this would go, but it's worth thinking about.
Contributor guide
Assessment
This issue has not been assessed yet.