Testing & evaluation
A passing test, a top score and a successful experiment leave a question open: what does the result actually establish? Follow the code, the task and the measurement back to their assumptions.
Why do tests pass when the program is wrong?
Start with a familiar green test. Separate matching an expectation from getting that expectation right.
Start reading ↗It passed. What could still be wrong?
Ask what was checked, then ask how the checker was checked.
Does a better score mean a better outcome?
Compare what a task covers with what happens when a system learns to chase its score.
Does the conclusion survive a different measurement?
Revisit a good result through experimental conditions, measurement boundaries and use cases.
Take a question into another field.
These links come from existing readings. They do not imply that two fields share the same standards of proof.
Familiar questions and real mastery
Doing well under familiar conditions may only mean recognising a pattern seen before. Both readings ask for a test in a new setting, whether the one being tested is a model or a student.
Check the passages on both sides
a valid environment, many repetitions, timely feedback, and thousands of hours of deliberate practice.At its core, expertise is recognition.A pure interface promises less
Turning a decision into a same-input, same-output computation lets the interface promise only the result, not call order or outside state. That is the other reading’s question: which behaviours should never have become promises?
Check the passages on both sides
a true functional interface, same input, same output.start seeing interconnections between things that could be independentFalling loss can hide a bug
The same micrograd walkthrough appears in both. One uses it to show that a falling loss does not prove the code right; the other uses it to explain learning by gradient. Knowing what the gradient computes is how you judge whether “getting better” is real.
Check the passages on both sides
you may have lots of bugs in the code and uh your network might actually workefficiently evaluate the gradient of some kind of a loss function