I can identify with this. However when I did my GCSEs and A-levels, a very large requirement of the project was the creation of a design spec and thorough docum

I can identify with this. However when I did my GCSEs and A-levels, a very large requirement of the project was the creation of a design spec and thorough documentation. The actual implementation was just one part, not the entirety. That the kid in the story says he had to go back and comment his code suggests he fell into simple trap of getting so carried away with what he wanted to do that the other major requirements were left by the wayside. I fell into the same trap when I wanted to do my database coursework with PHP and MySQL. I got so far in and realised that if I carried on, I'd never get the written work done. I did brilliantly in the exams, top marks in the class each time, but my desire to try and do something impressive brought my overall mark down. So I'm a web developer who got a C at A-level ICT. Of course since it was nearly 6 years ago when I left sixth form, and 8 when I left secondary school, the curriculum might have changed.