ColinJ
Puzzle game procrastinator!
- Location
- Todmorden - Yorks/Lancs border
A friend rang me in a panic the other day, having received an electricity bill for over £10,000! I told her that there was clearly a mistake and not to worry, it would be sorted out.
She said that she was worried that something might be wrong with her wiring causing massive electricity consumption, but I reassured her that even if she had every socket in the building powering electric heaters flat out 24/7, it would be impossible to use that amount of electricity. Was her flat unbearably hot? No - good! The meter reading must be incorrect - due to either a faulty meter or to a faulty reading of an accurate meter.
It seems that the problem was caused by somebody somehow misreading the first digit to be an 8, instead of a 9, something like that. As a result, npower's software blindly assumed that the reading had 'wrapped round' and happily calculated that ridiculous bill.
It's a damn good job that it wasn't a vulnerable old person who received that bill!
What I want to know is this ... How is it in 2012, that somebody specifies a system so poor that it doesn't flag up a problem like that, and what self-respecting programmer would blindly implement it without insisting that some sensible range-checking be included?
She said that she was worried that something might be wrong with her wiring causing massive electricity consumption, but I reassured her that even if she had every socket in the building powering electric heaters flat out 24/7, it would be impossible to use that amount of electricity. Was her flat unbearably hot? No - good! The meter reading must be incorrect - due to either a faulty meter or to a faulty reading of an accurate meter.
It seems that the problem was caused by somebody somehow misreading the first digit to be an 8, instead of a 9, something like that. As a result, npower's software blindly assumed that the reading had 'wrapped round' and happily calculated that ridiculous bill.
It's a damn good job that it wasn't a vulnerable old person who received that bill!
What I want to know is this ... How is it in 2012, that somebody specifies a system so poor that it doesn't flag up a problem like that, and what self-respecting programmer would blindly implement it without insisting that some sensible range-checking be included?
