Why we put geometry inside a coding unit instead of next to it

When we were designing the grade 3–5 band, the easy path was obvious: teach a coding unit, then teach a separate geometry unit, and let the standards-alignment spreadsheet claim credit for both. We didn't do that, and Polygon Maker is the clearest example of why.

The problem with side-by-side subjects

Kids are good at compartmentalizing. If coding class is coding and math class is math, a turn angle calculation in one doesn't automatically transfer to the other, even if the underlying concept is identical. We wanted a unit where a kid literally could not finish the coding challenge without doing the geometry.

What that looks like in practice

Polygon Maker asks students to draw an exact hexagon using a loop. To do that, they need the interior turn angle — 360 / sides — which means they're doing the math to unlock the drawing, not doing the drawing and then labeling it with math vocabulary afterward.

repeat sides_count times:
  move forward 100
  turn right (360 / sides_count)

That one loop is the entire lesson's math content. Change sides_count and the angle calculation changes with it — kids see immediately whether their arithmetic was right, because a wrong angle just doesn't close the shape.

Why immediate feedback matters here

A worksheet tells a kid they got the angle wrong three days later, after the teacher grades it. A polygon that doesn't close tells them in half a second, while they still remember what they were thinking.

How we chose which math to embed

Not every geometry standard survives this treatment. The ones that work best share a few traits:

1. The math produces a visible, checkable result (a shape closes or it doesn't)
2. The concept has a natural "variable" a kid can experiment with (side count, angle, length)
3. Getting it wrong is informative, not just marked incorrect

STANDARDS THIS MAPS TO

• CCSS 4.G.A.1 — classify shapes by properties of their lines and angles
• CSTA 1B-AP-10 — sequences, loops, and conditionals

Where this approach doesn't work

We tried the same embedding technique with fractions and it fell flat. Fractions don't have an obvious "does it close or not" visual check the way angles do, so we kept that content in its own, more traditional lesson format instead of forcing a fit that wasn't there.

A CLOSING NOTE

The lesson here isn't "always merge subjects." It's that blending only works when the math is genuinely load-bearing for the coding challenge, not decorative.