Built Right, and the Right Thing

Built Right, and the Right Thing

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

Verification asks whether the software does what was designed; validation asks whether the design helps children, and this article is about the first. Three promises a parent can check, why a rule is written before the code when much of the code is written with AI, and the person's review every change passes. Prepares the layers of checking that follow.

Engineers separate two questions. Verification asks whether the software does what was designed. Validation asks whether what was designed is the right thing: here, whether it helps children learn. A program can pass every check of the first kind and still fail the second. This article is about verification.

For a parent, verification is concrete. A topic should count as mastered only after the child has answered it. A fact learned weeks ago should come back for review when it is due. A lesson that no person has checked yet should stay locked for a school class. Each of these is a promise the design makes. Verification is how we find out, on every change, whether the software still keeps it.

Much of Fido's code is written with AI assistants; How We Build the School tells how we use them. A test written right after the code, by the same hand, tends to confirm what the code does rather than what it should do. So the rule comes first, written from what the behavior should be and never read off the code. And no change joins the software until a person has reviewed it.

The checks come in layers: written rules, tests of each part, replayed learning histories, walks through the screens, checks on the curriculum, and speed limits.

Keine Aufgaben fĂĽr dieses Thema.