DING. Wrong again. “Incorrect. The correct solution is x = 2.571, y = -4.143.”
“A clever number?” Leo hissed at the screen. “What’s clever about a number? Numbers aren’t clever. They’re just… there.” sparx. maths
That night, he didn’t sleep. He opened the browser’s developer console—a terrifying grid of code he usually avoided—and started tracing the network requests. Every time he submitted an answer, a little packet of data flew from his laptop to the Sparx servers and came back with a verdict: PASS or FAIL. But the FAIL was not based on correct maths. It was based on a floating-point comparison that had a 0.001 tolerance—except someone had written if (Math.abs(userAnswer - correctAnswer) < 0.001) when they should have written <= for boundary cases. And worse, the server was rounding the correct answer to 3 decimal places before comparison, but using 5 decimal places for the user’s answer. The correct solution is x = 2
Sparx’s eyes turned into little red X’s. “Not quite! Remember to check your signs!” They’re just… there