I've run the half twice and then the marathon last year. As others have said, only one decent hill which is a bit of a drag second time round, and then the Greenway part which can be soul-destroying. I can't see myself running it again. The organisation (barring the last minute cancellation of the marathon in 2012 due to conditions) has always been good.
Their course accuracy might be slightly suspect as well. On PowerOf10 my result from last year has been regraded from Mar, to MarNAD, which apparently stands for 'Marathon Near As Dammit'. Obviously close enough, but might be meaningful if you're using it as a qualifier for something.
As a non-techie, are we saying that UML can be used as a way of decomposing Samir's complex running ideas into something that the rest of the posters on this thread can understand. Maybe we can understand
Why the Sprint Start is the most effective racing strategy?
Why Smashing a mile at Ealing is the best form of recovery from injury
Just what effect does a bobble have?
For UML, you need to be able to draw them. We need a whiteboard!
Wow. What are the chances Ben. I would love for you to argue with my lecturer. This site may have been created using UML but it's hardly necessary is it. Do you really use it or are you just having a go? I really don't see the relevance it's like "did you have to use ink to come to that conclusion".
Yes, genuinely use it. A search of a well known professional networking site for my name will find you my professional profile, so you'll be able to see what I do and who for. If you want to pm me an email address I'd be happy to send you a real spec created using it for one of the biggest banks in the UK (which would have all the commercial labels removed for obvious reasons). When you're designing a large and complex system, UML is often the only decent way of decomposing requirements into technical specification that is technology agnostic. It also then can be given to development teams so they can understand the technical requirements of a system not just the functional. That spec above went to a 30 strong development team, along with a bunch of other documentation, for the implementation of the system.