Coding classes in Inverclyde

The model uses the listing's rough size, 110 by 20 metres, as a plain rectangle; everything else is invented. The river stands 6 metres above the dock floor and, for simplicity, stays there. Water enters through a sluice with an opening of 1 square metre. Torricelli's law says water rushes through an opening at a speed that depends on the square root of the height difference: a big drop means fast flow, a small drop slow flow. As the dock fills, the difference shrinks, so the flow slows down. The learner computes the volume, 13,200 cubic metres by our arithmetic, and then works out how long filling really takes.

The first half of the depth fills in under 20 minutes; the second half needs almost 48. The last 10 centimetres, a tiny fraction of the water, take nearly 9 minutes, because the height difference driving them is almost zero. The naive sum assumes the opening flow continues all the way, and for this kind of flow the true answer comes out at exactly twice as long. Learners can prove the factor of two with a little calculus, or simply trust the simulation once it agrees with the formula.

The simulation is where coding earns its keep. Stepping forward 10 seconds at a time matches the formula closely. With 60-second steps the water level overshoots and ends above the river, which is physically impossible. With 5-minute steps it overshoots further, and on the next step the program asks for the square root of a negative number and crashes. A quick fix, clamping the level at the river height, stops the crash but then reports the dock full at 60 minutes, more than 7 minutes early. The lesson: silencing an error is not the same as fixing the model.

That is why an Inverclyde teenager should still learn to code in 2026: to recognise when a quick fix has only hidden the real mistake. The longer argument is in why teenagers should still learn to code in 2026.