Speed limit in Bushy Park lowered to 20 mph

I wrote a few weeks ago that the speed limit in Bushy Park, Teddington, was 30 mph.  Royal Parks has now lowered the speed limit in Bushy Park to 20 mph to match that in Richmond Park.

Slower vehicles means greater safety for cyclists and pedestrians.  But it also means a greater chance of running into the back of a slow moving car (or needing to overtake) if you’re used to riding through the park at a fast pace, so be careful.

Police are apparently spending more time in the park to ensure that road users are adhering to the new speed limit.

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

Apple, Adobe and developing for iPhone OS

A spat between Apple and Adobe has over the last few days become one of the biggest stories on tech blogs and forums across the internet.  There’s been so much written and argued about it that I almost feel this wouldn’t be a proper blog unless it included my take on things, so here goes…

The issue at hand is a change to Apple’s iPhone Developer Program Licence Agreement, which states:

“3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).”

This means that if developers want to create applications for the iPhone, iPod Touch or iPad, Apple essentially requires them to use Xcode, its very own integrated development environment (IDE).  Xcode includes a software development kit (SDK) for iPhone OS, which makes it easy for developers to write native applications that can take advantage of all of the technologies and broad range of application programming interfaces (APIs) that are included in the OS.  The APIs are well documented and registered members of the development program have access to many additional resources aimed at making the development process easier.

What developers are not permitted to do is write their code in another IDE using a non-native language and non-native APIs, and then have their code translated into Apple code by making use of an intermediary layer in their applications.  And that is something that Adobe is not happy about.  Why?  Well, Adobe have built a new feature into Flash which allows Flash developers to export their code to iPhone applications.  The new feature means that Flash devs can create iPhone apps from their ActionScript code without needing to know anything about Objective-C, Cocoa Touch or any of the frameworks or APIs that Apple includes in iPhone OS.  Apple’s new condition is bad timing for Adobe as the iPhone export feature is the new big thing in Flash CS5, due to be released shortly (they are already taking pre-orders).

There are all sorts of arguments and opinions flying about, hysteria, anger, accusations.  It’s all be rather dramatic.  Here are some points that I think are worth considering:

Flash devs would love to take advantage of the huge market for iPhone applications, but don’t want to have to move out of their comfort zone

Some Flash devs will argue that Apple is wrong to be ‘locking in’ developers to Apple’s APIs and that it is anti-competitive behaviour that will ultimately result in alienated developers, less development taking place and less choice for customers.  If that were the case, then surely the platform would be doomed to failure and worth avoiding at all costs, would it not?

I can understand their disappointment, having been promised free access to the iApp market by Adobe only to find out that Adobe’s solution has never had Apple’s blessing.  It must have been a dream come true to think that they could start selling applications through the iTunes App Store without having to spend any time at all on building an understanding of Apple’s frameworks.  Too good to be true, even.  Well that’s exactly how it’s turned out.  Adobe have really screwed over their own customers by making promises they couldn’t keep, so it’s probably just as well for them that this has surfaced before everyone rushes out to buy CS5.  Had Apple supported Adobe’s plans and then backed out, that would be a different story, but Apple and Adobe have not worked together on this at all (not that I have any insider knowledge, but from what I’ve read nobody has reported any such circumstance).

Learning another programming language, new frameworks and APIs, is an overhead, an investment one makes to increase skills and broaden abilities.  There are plenty out there to learn, all with different features, advantages and potential markets.  What you choose to learn has some impact on what markets are available to you, and of course the more you learn, the broader your options.  If you want to write applications for iPhone OS and take advantage of the huge market that Apple has created, then learning Objective-C and Apple’s IDE is an investment in time that you need to make.  Following Apple’s guidelines and programming natively with Apple’s APIs is a robust and informed way to develop good quality applications that can directly take advantage of all of the features included in the OS.  Many developers from non-Apple backgrounds have already started developing for iPhone OS and met with great success.  For developers experienced in object oriented program design, or C++, the transition isn’t that difficult.

Developers for iPhone OS have churned out over 145,000 applications since Apple released the first SDK in 2008.  That’s an impressive statistic.  Granted many of them would already have had knowledge of developing Cocoa apps for OS X, which is an advantage, but many others have not.  There has been some noise about the App Store approval process, but largely the existing iPhone developers do not seem to feel ‘locked in’ as some of the Flash mob would have us believe.  To have produced that many applications in under two years has certainly not limited customer choice either.  If any current Flash developers want to experiment with iPhone programming then they should take the plunge, join the Developer Program and start learning the ropes.  To gain access to a big new market for little to no effort is a bit unrealistic.

Apple wish to maintain quality

As a long time Mac user, I’ve experienced a lot of applications that have been straight ports from other platforms and they are, for the most part, pretty awful, so I can understand from this why Apple wants to keep these kinds of apps away from its mobile devices.  Apple have created a good SDK with APIs that help developers to produce applications that fit Apple’s style guidelines and ultimately provide a superior user experience.  Anyone familiar with OS X development will know how much Apple push their developers to produce clean and intuitive interfaces.  They even have a document entitled “Apple Human Interface Guidelines” which specifies how applications should be designed to fit visually and functionally with OS X.  This is not an attempt by them to control developers – anyone can release an OS X application – it’s just that those applications which follow the guidelines will be a better fit with other applications including the OS, and will have a more intuitive feel for the end user.  This is all good for developers as their apps will likely receive better reviews and recommendations, thus resulting in more sales (I know there’s more to making a successful app than just having an intuitive interface, but that’s another issue).  Apps that don’t follow these guidelines, like those that have been ported from other platforms and not coded natively, stick out like a sore thumb.  They are generally bland, clunky and difficult to understand.

Why would Apple, having gone to a lot of effort to produce a solid SDK, want apps being sold for their mobile devices that have not been developed natively?  They are going to want to keep a certain amount of control on what goes on to their devices, as if the floodgates opened and half the apps on the App Store ended up being substandard ports from Flash or other IDEs, it would reflect badly on Apple’s devices and result in fewer sales.

It could be argued that the App Store approval process should weed out any such apps.  It could also be said that some of the apps currently available in the App Store are not particularly good, even if they have been developed natively.  There is unfortunately always going to be a range of quality amongst applications, as with everything in the world.  That can’t be avoided.  But if Apple were to start rejecting apps purely on the basis of whether they liked them or not, they would eventually alienate a huge number of developers who had put time and effort into creating native applications.  That wouldn’t be fair.  Apple therefore need to maintain some objectivity in their approval process.  This new rule is one such flag of objectivity.  Apple wish to keep app quality high, and to that end they desire their developers to code natively for iPhone OS.  It’s perfectly reasonable.

Developers should not be reliant on Adobe for the feature set available to their apps

Imagine that Apple were to allow iApps to be ported from Flash.  The pool of developers would be distilled with the new Flash-based crowd.  Some existing developers could stop coding natively for iPhone OS as they would be able to create their apps in Flash and distribute them as web apps at the same time, reaching a greater audience.  Then Adobe would add Android, Blackberry & other export options to Flash.  Soon enough Flash would be the only IDE in use and platforms including, but not limited to, iPhone OS would be at the mercy of Adobe.

If Apple were to introduce new features and efficiencies to their hardware and APIs, they would have to wait for Adobe to implement them in its Flash translation layer before the features would really become available to developers and end users.  Even the most willing and motivated of developers would not be able to get around that, they would have to wait for Adobe to add the capabilities before they could take advantage of them in their apps.

In the end, Apple would lose sales and credibility, and good developers would get screwed because they wouldn’t be able to outpace their competitors in updating their apps to take advantage of new features.  Everyone would become ‘locked in’ to Adobe (so much for developers being locked in by Apple).  Given Adobe’s poor history when it comes to timely bug fixes and support of its OS X applications, I do not think that this ‘lock in’ would be a nice place to find yourself, whether you’re Apple, a developer or an end user.

Bear in mind also how Apple and Adobe make their money.  Apple sells hardware and software.  They sell the iPhone, the iPod Touch and the iPad, all of which run on iPhone OS, and they additionally take a 30% cut of App Store sales.  Apple needs to keep its products desirable so that they can keep sales up, so it’s in their best interests to ensure that what’s running on their products is a credit to them.

Adobe on the other hand, sells design software, including Flash.  They make no money from sales of Apple’s mobile devices.  They therefore have no motivation to ensure that Apple’s devices or the applications that run on them remain at a high standard.  The fact that they’ve produced a feature that can export ActionScript from Flash to iPhone applications has nothing to do with them wanting to support Apple’s platform, or work together with them to produce great products.  Adobe has just seen that the market for iApps is massive and that by including their new export feature in the next version of Flash they will generate substantial sales of CS5.  These would include sales to many existing customers that would not otherwise have found a compelling reason to upgrade from a previous version.

Another point to note is that if you are a UK customer, Adobe Flash CS5 will set you back £653.30 for the boxed edition or £672.76 for the download (which make no sense to me at all).  Apple’s Xcode, on the other hand, is free.  You just need to have a Macintosh.  Apple does not stand to make anything directly from Xcode, so this is not a battle against Adobe for commercial success in the iPhone OS developer tools market, as such a market does not exist.  They are therefore not abusing any monopoly as some people have been quick to insinuate.  Apple provides all of the tools that developers need to make good iPhone apps and Adobe’s meddling would do nothing but devalue the market that Apple has built from scratch.

Apple is completely within their rights to limit iPhone OS development to their IDE.  If developers don’t like Apple’s stance then they can happily go and develop for other platforms and buy other products.  But if they want to be in on the action and have a taste of the lucrative iPhone OS-based mobile application market that Apple has created, then they should take the plunge and move to Xcode.

These are my just views on the issue.  Many others have written on this topic far better than I.  Here are some links for further reading:

John Gruber at Daring Fireball

Thomas Fitzgerald

Jason Snell at Macworld (scroll down to the heading “Blocking out Adobe”)

Steve Cheney

Jean-Louis Gassée on Monday Note

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

New domain aeroprofile.co.uk and self-hosting

If you’ve not already noticed, I have mapped the domain aeroprofile.co.uk to my blog at aeroprofile.wordpress.com, so you can update your bookmarks, links and feeds.

I’m looking to migrate this from wordpress.com to a self-hosted blog with a new design sometime soon, so watch this space.

You can start your own WordPress blog by visiting wordpress.com, or find out more about starting a self-hosted WordPress blog at wordpress.org.

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

New tyres for the Brompton

Other than a dose of chicken pox in the family, Easter brought with it a hearty mix of good food, good wine and too much chocolate.  But despite these obligatory indulgences, I’ve been in no state to work their lingering effects out of my system as I’m still off the bike.  It’s a bit depressing and I hope it won’t be for too much longer.  Planet-X are collecting my broken wheel today (delayed a bit by the holiday weekend) and I have ordered a new derailleur, opting for Shimano Ultegra 6700 rather than 105.  I also ordered a new FSA bottom bracket as the bearings on mine are sounding pretty bad after almost two years use.  Hopefully I’ll be back up and running soon.

In the meantime, I’ve been commuting on my old mountain bike on wet days and on the Brompton on dry days.  On Sunday I put some new tyres on the Brompton.  They are Schwalbe Kojak 32-349 (16″ x 1.25″).  These tyres are narrower and slicker than the standard Brompton tyres which they replace, and although I haven’t fully put them through their paces yet, they do feel nice and fast.

Previously, people who wanted to ride their Bromptons at a fast pace kitted them out with Schwalbe Stelvios, but Schwalbe stopped producing these in a 16″ size in 2008.  The Kojak, which was formerly a fat but slick city cruiser type tyre, started coming out in 2009 in a narrower version which provides a good substitute for the departing Stelvio.  The Kojak features a Kevlar bead which aids puncture resistance and a new rubber compound which improves grip, particularly on wet surfaces.

Schwalbe Kojak 16" x 1.25"

Anatoly Ivanov has written up a good review of the Kojak after switching his Brompton over from Stelivos.

I can give a better opinion once I’ve ridden on these for a while, but for now the change to a narrower tyre has meant that I can get up to speed more quickly and keep at a high pace with less effort.  With these tyres, I might have to take the Brompton on a Friday Night Ride to the Coast sometime!

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

Easter chicken pox

I’m back at work after the long weekend.  My brother visited for a few days, which was nice.  The weather was patchy, but did include some nice sunny spells.  We, however, spent most of our time indoors with a little girl with chicken pox.

She got a high temperature early last week coupled with a number of red spots.  She was a little miserable to begin with.  After a few days she was feeling ok, but rather bored to be predominantly house-bound.  We could go for little walks outside, but couldn’t really take her to the playground or shops where she might end up being in contact with other children.  So a bit of extra attention management was necessary.

Other than that, the only thing that chicken pox requires is routine dabbing of the spots with calamine lotion.  This is supposed to ease the itchiness and make the patient more comfortable.  We understand the benefits, but it’s hard to reason with a two-year-old who just doesn’t like the look of the stuff.  We only managed to apply the lotion on one occasion.  She kicked up such a fuss every other time it was suggested that we weren’t able to get any onto her, not willingly at least.  We managed to sneak a bit on when moisturising after a bath one night, and we almost convinced her to have some put on by playing doctors.  I thought I’d been terribly clever to use role play to achieve this.  She removed her trousers and top happily enough, however as soon as I, playing the doctor, moved to dab her with lotion soaked cotton wool, she decided to stop playing.  So close, but not quite there.

She’s almost back to normal now, just a few lingering spots that are waiting to fully heal.  The only hard part is convincing her to stop scratching and scab picking!

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

FNRttC: March 2010 to Brighton Photos & Videos

YouTube video of the ride to Brighton (9:40) by Andy Allsopp:

Video by tdr1nka

Photos by topcat1

Photos by Tim Hall

Photos by clivedb

Photos by zigzag

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

FNRttC: London to Brighton and back

Friday 26 March saw the biggest and smoothest ride in the recent history of the Friday Night Ride to the Coast.  This write-up is a few days overdue – I’ve been a bit sleepy and a bit busy since Saturday to get this written, so sorry for the delay.  Anyway…

I got home from work on Friday and settled down for a couple of hours sleep.  I never get any real sleep when I try so early in the evening (even after avoiding caffeine all day), but lying down for a rest does help a bit.  I got up about 20:30 and headed downstairs for a double espresso and pasta with tuna, then checked the weather forecast.  On Thursday, Metcheck had been forecasting a dry night with a very light southerly, which was quite favourable, but during Friday the forecast had started to indicate rain.  It was still showing some rain, but not terribly much. That kind of forecast makes it difficult to decide what to wear and what additional clothing to carry.  At least I knew how cold it was going to be – no less than 4C.  The almost complete cloud cover would prevent it getting any colder than that.

By the time I’d had a shower it was 22:00 and had started raining quite heavily outside.  The rain only lasted a few minutes, but it meant that the ground was going to be wet and more rain could be coming, so I slapped a race blade over my back wheel.  I didn’t want to carry a bag with me so I set about organising my pockets to squeeze in my waterproofs, phone, keys, money, short-finger mitts and a bunch of gels.  Spare tubes, CO2, other tools and things were safely stowed in the little bag under my saddle.  Just one more espresso required.

I set off for Hyde Park Corner about 22:40, riding across Richmond Park and up through Barnes, Hammersmith and High Street Kensington.  The crowds were already building up under the Wellington Arch as dozens of cyclists arrived from around London and the local railway stations.  This FNRttC was a little different to usual.  About 60 regulars were attending and escorting a contingent of 65 riders who were fundraising for the Martlett’s Hospice.  This made the ride an official CTC event rather than an informal ride, so everyone had to sign in.  We had a quick safety talk and then set off at midnight around the Hyde Park Corner one-way system, through little roads to Sloane Square and across Battersea Bridge towards Clapham Common.

A field of 125 riders is a lot larger than the FNRttC had seen before and given that half of the participants were new to the concept of night riding, with some on heavy and/or dodgy looking bikes, one could be forgiven for having a little apprehension about whether or not the ride would run to schedule.  The rides routinely arrive at the coast an hour behind schedule with half the number of riders, so how was this one going to fare?

Against the odds, this was probably the smoothest running FNRttC to date.  It must not be forgotten the Simon Legg is quite a legend.  He had beefed up the group of Tail-End-Charlies (TEC) so there was a high level of expertise available to anyone who suffered a mechanical problem.  Canisters of compressed CO2 were in abundance to speed up puncture repair (perhaps this should become a permanent feature).  There were plenty of wayfinders at the front of the pack ready to give directions at intersections and mark significant potholes.  Riders were appearing on Madeira Drive in Brighton by 8:00 am, which wss right on schedule.  It couldn’t have gone much better!  Let that be a lesson to my pessimism.

I did my share of wayfinding along the route and marked a big pothole in the middle of Lonesome Lane, just south of Reigate.  Standing in the middle of the road signalling for riders to go either side of me, I felt like I should have been blowing a whistle and holding a little triangular flag above my head, like you see in front of traffic islands in the Tour de France.  I was really impressed with all of the riders I saw coming past me while I was wayfinding.  Even towards the end people were looking fairly fresh and smiley.  The half way stop at the scout hut in Horley was instrumental in keeping both spirits and carbohydrates high.  The Martlett’s volunteers pouring tea and coffee, and providing sandwiches, cakes and bananas were marvellous.  It was a well deserved rest for everyone and well-timed as it came just before Turner’s Hill.

To the half way point there had been two drop-outs.  One was a Martlett’s girl who was clearly struggling from the beginning and ended up in the minibus (or sag wagon) early on.  The second was Charlotte, who I recognised from the ride to Bognor Regis in August 2009.  She had been riding a brilliant looking penny farthing, but had come into mechanical difficulty after one of her cranks fell off after descending Reigate Hill.  Despite some attempts, it was unable to be fixed so she unfortunately had to pull out and ride the sag wagon the rest of the way to Brighton.

There were some other interesting bikes on the ride too.  One enormous contraption fabricated from at least three bike frames set the rider about two and a half metres above the ground.  At the other extreme, a recumbent trike with a swept back windshield placed the rider’s head lower than the height of a 700c wheel.  My friends Wheeled Weenie and Cathy rode the whole route on a tandem, the first time either of them had ridden on such a bike.  Quite an achievement.

The tallest bike I've ever seen approaching the summit of Ditchling Beacon

The weather was dry the whole way to Brighton and it wasn’t too cold.  There were several stops along the way but none were too long.  Everything flowed nicely.

A few miles before Ditchling, I noticed that my front tyre had lost a lot of air.  It wasn’t flat, but was quite soft.  I decided to top it up and keep going.  By the bottom of the Beacon it had gone down again, so I stopped to change the tube and then it was up the hill.  I’ve ridden Ditchling Beacon a few times, but this time was the hardest I remember.  My fitness is just not what it was before the winter and it was quite an effort getting up there.  I resolved at that point to start featuring more big hills in my training.

After the Beacon, it was a nice ride past the golf club and down into Brighton for a full veggie breakfast (with hash browns) at the Madeira Café.  There I got chatting and managed to put a lot of faces to names I was familiar with from the CycleChat forums.  It was nice to meet lots of new people.  I also managed to meet on this ride another Willesden CC member who lives not far from me in Twickenham.  He noticed my club jacket while we were preparing to depart at Hyde Park Corner and came over to have a chat.

After some breakfast and chit-chatting, a bunch of us, about 12 I think, got ready to cycle back to London.  At that point I discovered that my front tyre was gone again.  It looks like a little flint stuck in the tyre must have been poking through to the interior just enough to cause a slow leak in the tube.  So I changed the tube again and with no spares left, we set off north.

We ascended what must have been one of the steepest streets in Brighton, up under the entrance to the railway station, and continued from there towards Devil’s Dyke.  Going down the other side of the Dyke was fun and I clocked about 75 km/h!  The route we took followed some beautiful little country roads that were a pleasure to ride through after having been up all night.  But there were a lot of hills and one of our number bonked half way up one of them, opting to stop for a long rest before finding the nearest railway station.

We stopped for a while in a little village and grabbed some food and drink to keep us going, then we jumped onto an A road and picked up the pace past Crawley and Gatwick.  The group then split with four of us heading north-west and the others heading north-east towards Bromley and central London.  We said our goodbyes and Mistral guided us back onto quieter roads towards Dorking.  Along this stretch we encountered our first rain since leaving Hyde Park Corner the night before.  As it got heavier we stopped to neck some more gels and put on our waterproof jackets.  A little later the rain had stopped and I was starting to get a bit hot in the little sweatbag I’d zipped onto myself, so off came the jacket.

With Box Hill towering upwards on our right, we diverted left and took a nice narrow country lane towards Stoke D’Abernon.  We started to see a number of other roadies out for their Saturday training rides.  Mistral told us that there would be one last hill that is a little steep but not too long.  This last hill resides on Chapel Lane and its gradient is over 20% for a good portion of the climb.  After almost 200 km and no sleep, ‘not too long’ felt like it would never end and I had to summon every last bit of will power to keep myself going.  I got to the top in one piece and took a good long breather while waiting for the others.

We rode past Stoke D’Abernon towards Cobham and past the Chelsea FC training grounds.  The road inclined slightly as we approached a bridge over the railway line and then disaster struck.  As I put on a little acceleration, I heard a massive clunk, my back wheel stopped spinning and I couldn’t move the cranks.  I managed to unclip and get off the bike without falling.  My first guess was that one of the rubber straps from my mudguard must have gotten caught in the spokes, but on taking a look it was in exactly the right position and the straps were well clear of the wheel.  I took a closer look and then saw that a spoke on the non-drive side had snapped up near the rim and flown into the chain.  It had then been wrapped around the underside of the cassette and gotten trapped between the chain and one of the jockey wheels causing the derailleur to bend out of shape.

A non-drive side spoke snapped at the rim and wrapped itself under the cassette, becoming trapped between the chain and a jockey wheel and causing the rear derailleur to bend out of shape

I couldn’t believe it.  Not only was I almost at the end of the ride (about 20 km remaining), but the wheel was almost brand new, received from Planet-X in late February.  I really didn’t expect to get broken spokes so soon after buying the wheels and in normal riding conditions.  I’ve even been extra careful in avoiding bumps and potholes since getting the wheels as I haven’t wanted to cause them any damage.  I was gutted.

The four of us all stopped and had a think what we could do.  We removed the derailleur, which was bent well out of shape.  We managed to get the broken spoke out and then set about shortening the chain with a view to me riding single speed the rest of the way home.   That was no good though.  The wheel was way out of true, so that was the end of the road for me.  I thanked the guys and plodded off towards the railway station, which fortunately was quite close by.  A 20 minute wait got me onto a train to Wimbledon where I grabbed an espresso, switched trains and then walked home from Norbiton.

I got home about 17:00.  Recovery drink?  Bit late for that, should have had it just after I stopped pedalling.  Had a shower, got into my compression tights and cooked some more pasta to go with the remaining tomato/tuna sauce from the night before.  Visited Wiggle to see what a new derailleur was going to cost me.  I could always try bending the current one back into shape, but I don’t feel too comfortable with that.  Maybe I could use this as an opportunity to upgrade from 105 to SRAM Rival or Force (or maybe Red, are there any specials on?)  Of course I’d need to replace the shifters in that case (how much are they?  Hmm, quite a lot.  Been awake too long, starting to imagine silly things, spending money I don’t have.  Better stop looking before I press Buy.)  Felt sorry for myself and set my Facebook status accordingly.  Maybe I’d get some sympathy.  Opened a bottle of Gran Bombero, the older, wiser sibling of my favourite El Bombero.  That’s nice.

Managed to stay awake until 21:00 and even thought for while I might be able to have a cosy evening in with wife, wine and a film, but that was delusional.  My head hit the pillow and I was out in an instant.

Mechanicals aside, I had a great night/day out.  The FNRttC was phenomenal, the weather was ideal, the ride back was fun and I made some new friends.  It couldn’t have been much more enjoyable!  The Martletts riders were an inspiration and the charity director who came and shook all of our hands on Madeira Drive was overjoyed with the success of the event.

But I now have a broken bike.  I emailed Planet-X telling them what had happened.  Dave Loughran got back to me saying that they get very few problems with their Model B wheels but that he’d like to take a look at it.  I’m going to get the wheel and broken spoke boxed up tonight and sent back to them.  I hope they’ll be able to fix it up under warranty.  But for now, I’m off the bike.  I’ll keep you updated!

The route we took from HPC to Brighton can be found on Bikely.

Registration for the next FNRttC on 30 April is now open.  The route is to Southend-on-Sea.  More details here.

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

Andy Allsopp's London-Edinburgh-London Adventure

I just received in the post my copy of Andy Allsopp‘s book ‘Barring Mechanicals – From London to Edinburgh and back, on a recumbent bicycle‘.

Andy is one of my friends from the Friday Night Ride to the Coast (FNRttC) and I met him properly in November 2009.  As we rode through the night towards Brighton, in cold and wet conditions, he was telling me how he had ridden his recumbent from London to Edinburgh and back in July 2009.  It wasn’t just something he’d done for a laugh, but was an Audax event that takes place every four years and draws cyclists from all over the world.

Andy Allsopp: Barring Mechanicals - From London to Edinburgh and back, on a recumbent bicycle

An Audax, or randonnée, for those of you not in the know, is a non-competitive endurance cycling event in which participants aim to complete an unmarked route within a set time limit, collecting stamps at ‘controls’ along the way to prove that they’ve followed the course.  The London-Edinburgh-London (LEL) is Audax UK‘s flagship event with a distance of 1,400 km and a time limit of 116 hours and 40 minutes, which is a bit under five days.  The LEL is a ride that I have recently found myself thinking about quite often.  I haven’t really taken part in Audax events before, but I did enjoy a bit of cycle touring when I was a teenager.  The next LEL is in July 2013 and I think I’d like to have a go.  Watch this space.

Bits of Andy’s story I had already read in his LEL forum thread on CycleChat, but it’s nice to have a printed copy containing a foreword, which gives a bit of history that I wasn’t aware of (and mentions a few familiar names), and a number of pictures and charts.  It’s a good read, so if accounts of heroic two-wheeled battles against Mother Nature, mechanical failure and sleep deprivation are your sort of thing, then go and buy it!

I’ll be seeing Andy and the rest of the bunch on tomorrow night’s FNRttC.  The destination is Brighton and this month’s edition is a rather special one.  This is the first time that a FNRttC is being combined with a charity fundraiser.  Martlett’s Hospice are sending 65 riders who are all taking part to raise donations for the charity via sponsorship.  They will join 60 of us more regular FNRttCers as we depart Hyde Park Corner at midnight and pedal to the south coast via Sloane Square, Clapham Common, Reigate, Horley and Ditchling Beacon.  Whilst this is a nice social ride for us regulars, it could be a big challenge for some of the fundraisers, so our job is to provide technical support, guidance and most of all encouragement.  The Hospice is putting on mid-way refreshments at a Scout Hut in Horley for this one rather than us making a café stop.

Although I’m not fundraising for this ride, some of the regulars have decided to and I’ve sponsored Greg Collins.  If you would like to make a donation to the Hospice, you can find Greg’s Just Giving page here.

I’ve been keeping a good eye on Metcheck for the last week to see what kind of weather we’re going to be in for tomorrow night.  It’s gone from extremely heavy rain all night, to less than a millimetre, to constant but moderate rain and a headwind, to the current forecast which is for no rain at all and a very light, near negligible, headwind.  That’s quite a nice prospect, so I hope it doesn’t change again!  Whatever the weather though, it’s bound to be a fun and memorable ride.  The last FNRttC I did was in November and it was very cold and we got rained on very hard.  One person from work who I had convinced to come along had to abandon half way and two others made it to the end but didn’t seem too impressed.  It was still a memorable ride, though maybe for all the wrong reasons.  Wet and cold together are not so fun.

But, of course, if Andy Allsopp can find it in him brave the elements day and night for 116 hours solid, then I’ve no excuse for being bothered by a little spot of rain!

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

Almost Box Hill

I rose early this morning and headed out on a casual ride to Box Hill before work.  My intention had been to ride from Kingston through New Malden and Epsom, along  Headley Road at the foot of Box Hill, up the Zigzag, down the other side to Headley and then home again via Leatherhead, Oxshott and Esher.  However, travelling on some unfamiliar roads without a GPS on my handlebars, I quickly made a lot of wrong turns and had to spend quite a bit of time doubling back and stopping to check the map on my phone.  This cost me so much time that once I’d reached the bottom of Zigzag Road, I couldn’t even enjoy climbing it as there was no way I’d make it to work on time if I did.  I also had to cut short the return, opting for the A243 from Leatherhead through Chessington and Surbiton rather than the marginally nicer and slightly longer A244 and A307 via Esher.

Nevermind.  I now know a few more roads and intersections so I will be able to fit more in next time!  Here’s the route I took (about 50 km):


View Larger Map

It was quite a lot colder at 6 am than I had anticipated, about 3 degrees celcius, so I wore long finger gloves and a thermal skull cap.  It was nice and dry though, with a light southerly.  In fact, the southerly might have been a bit stronger than I had thought, as I felt quite a lot faster on the northbound return.

A friend from the Cheam and Morden CTC once told me that for the last fifty years Headley Road has often been referred to by cyclists as ‘Little Switzerland’.  “I shan’t describe this road,” he told me, “not because I think this would reduce the pleasure of riding it, but because I couldn’t do it justice.”  It is delightful.

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn

Ignorant drivers

Instead of going to Richmond Park this lunch time, I decided to have a gentle ride on a flat loop from Teddington along the north side of the Thames to Shepperton, over the bridge at Walton-on-Thames and back to work via Hampton Court and Bushy Park (about 22 km in total).  The weather was cloudy but warm with a decent south-westerly.  The first half of the ride was fairly gentle, but I decided to increase the pace a bit for the remainder.  I hadn’t been out that way before so it was quite nice to learn some new roads.


View Larger Map

This map is for a clockwise loop, but I actually rode it anti-clockwise.  For some reason Google Maps wouldn’t let me plot the route northbound through Bushy Park.

All had been going well until I got into Bushy Park.  Bushy Park has a road running through it with a lane each for northbound and southbound traffic.  Near the south end the road splits around a circular pond with a diameter of about 100 metres.  The lanes of traffic split at the pond with one lane going around each side.  At the north and the south ends of the pond it is possible for traffic to continue around the pond by joining the opposite lane instead of continuing ahead.  Traffic performing such a manoeuvre, however, must give way to any traffic already on the lane they are entering.  I know this all too well as I had once powered it hard southbound through the park and wanted to circle the pond without losing any momentum so that I could continue with the effort all the way back to the north end of the road.  Unfortunately there was a car coming north as I got to the bottom of the pond and so I had to slow right down to let him through.  A shame, but fair enough.  The give way requirement is quite clear with double white lines painted across the road and of course a give way sign (you’ll be able to see this if you switch the map to satellite and zoom in).  One of the good things about the road is that the speed limit is 30 mph as oppose to Richmond Park’s 20 mph.  That means it’s usually possible to ride at a fast pace without having to slow down for or overtake traffic.

Today I happened to be heading north and I was approaching the pond at about 35 km/h.  Just as I was getting to where the lanes split a small car coming the other way indicated a right turn into my lane.  To my complete surprise they didn’t stop at the give way, they didn’t even slow down, they just went straight through causing me to apply my brakes suddenly so as not to hit them.  I have witnessed plenty of poor driving before, but it’s been a long time since I’ve had such a close call when going at that sort of speed.  I was astounded at the drivers reckless driving and sheer disregard for pretty basic road rules.  I shouted my disapproval, “You’re supposed to give way!”, followed by “Idiot!” when they accelerated ahead.

The car was small and a bit old-looking.  A girl in her late teens or early twenties gave me a stupid look as they went off ahead of me.  I was so furious.  I chased after them at 45-50 km/h all the way to the north end of the park.  When I got there a queue of traffic was waiting to exit through the park gates so I stopped next to the car and knocked on the window.  Two middle aged ladies were sitting in the front.  I said, “That was not a roundabout, you had a give way.”  Had they said sorry I would have let it go and continued on my way.  That’s what I would have expected from the majority of drivers, and I can understand to some degree that a road circling a round pond could be mistaken for a roundabout where one is expected to give way to the right (although that’s not a valid excuse for drivers ignoring road signs and markings, but it could be the cause of a driver misunderstanding the intersection).  Instead I got a nasty, “Why don’t you grow up?”  They kept edging the car ahead to get away from me, but I continued, “What?  Are you trying to kill me?  You were supposed to give way to me”  I just got a load of abuse in response.  And then one of them shouted out, as they finally pulled away from me around the corner, “Didn’t you see the indicator?”  I could only follow it up with another shout of, “You had a give way!”

It reminds of two things.  The first is an incident that happened to a friend of mine some years ago.  He was cycling home from work along a straight piece of road when an older woman in a car wanted to turn onto the road from a side street on the left.  Despite seeing him coming, she turned straight out in front of him.  He had insufficient time to come to a stop and went straight into the side of her car putting a large dent in one door, damaging his bike and giving him a knee injury that took months to get over.  When he asked her what on earth she was doing turning into the road in front of him like that, she replied that as she was indicating, it was his fault for not slowing down to let her through.  The ignorance is astounding.  Would she have done the same thing if he had been a bus?

The second thing this incident reminds me of, and on a lighter note, is a piece of Jasper Carrott stand-up in which he was talking about his gran’s driving skills (update: it’s actually his mother-in-law, not his gran, and you can hear the clip on YouTube).  She knew every detail of the road code by heart.  For example, she knew that when pulling into the road from a parking bay, you need to check your rear-view mirror first (to see that nothing is coming, of course).  But to her there was no reason behind it, that was just a step that you had to take, so even if a ten foot truck was coming she would think, “I’ve looked in my mirror so it’s safe to pull out” (sound of screeching brakes).  Despite the humour, people like this actually exist.

This is the kind of ignorance that contributes to so many injuries and fatalities.  There exists a set of drivers that believe cyclists are required to give motor vehicles the priority on all occasions.  I see plenty of bad drivers, particularly those who fail to indicate (or indicate after they have begun turning), but the number of good drivers I see on a daily basis well outweighs the bad ones.  However, this breed of ignorant road users, the likes of which I have experienced today, really are the worst of the worst.  I wonder how they ever managed to get driving licences (or if indeed they hold licences).  In fact, it makes me more insistent that drivers should be retested every so often to ensure that driving skills and knowledge of the road code remain at a high level.  This whole incident has really got my blood boiling.  I can accept that people make mistakes and a lot of drivers I see do take corrective steps when they realise they’ve done something wrong.  But to encounter a torrent of abuse from someone who has just put my life at risk by failing to stop at a give way sign is infuriating.  Writing this has helped to calm me down a bit though.  In hindsight, I wish I’d thought to pull my phone out and take a picture of the car & licence plate before confronting its driver.

What can we do about this rare but dangerous strain of road user?  Petition the Government to provide a vaccine perhaps?

Share this post:
  • email
  • Twitter
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Posterous
  • Technorati
  • LinkedIn