This Blog Has Moved!

Right, so yes, five years ago I moved to github pages, and never bothered to redirect any of these pages there. Now I've moved on from there, and... Finally I am using my real domain, trishagee.com . My blog is now at trishagee.com/blog .  See you there!
Post a Comment

Cyclist tribes

Living and working in central London, you quickly learn that the fastest way around town is to cycle.

My extensive research into this activity has shown there are a number of different cycling tribes. Of course, I have split them into the two groups that are most appropriate to me: 1) slower than me and 2) faster than me. You can probably tell what sort of a cyclist I am by my attitude to the two groups.

1. Slower than me:
  • Wicker shopping basket. Doesn't matter what the rest of the bike looks like, or the biker, I will always try to get ahead of these.  The extra scary ones are the women in flowing dresses who might be university professors.
  • Boris Bikes.  When there's a tube strike, Avoid At All Costs.  These people probably haven't been on a bike since they were in school, and it shows.
  • Hoody (always a male) on a BMX-style bike with the seat far too low, riding in too low a gear, with baggy jeans that show their... well... everything. Never have lights on their bikes.  Always has a satchel / record bag for maximum inappropriately-dressed-for-cycling points. These buggers are a pain because they never obey traffic lights and will join the road from the pavement on either side, cutting you up in the process. Getting past them is easy, keeping them behind you is much harder. 
  • Not wearing a helmet. Probably not a serious cyclist, so probably easy to overtake. A similar category to the hoody, doesn't obey traffic laws and enormously unpredictable. Otherwise known as an organ donor.
  • Wearing a skirt. Of course, this doesn't apply to me. In the same category: jeans, sandals, high-heeled shoes (not all at once). 
2. Faster than me:
  • Cleats. If you have cleats on the bike I'm going to let you go first from the lights. You'll be fast and possibly suicidal when weaving through traffic.
  • Lycra, especially on a guy. Even if they're not faster than me, they will always overtake, and always pull in front of me at lights. It's an ego thing.  Something about those tight shorts possibly.
  • Panniers. Generally, but not always, a “proper” cyclist, even if they're on a rubbish bike. These guys have experience.
One to watch: businessman in a suit on a Brompton. You can't trust these guys, they can be deceptively fast. It's always embarrassing to be overtaken by them. How do they not sweat into their Armani?


Who does that leave?

Well, my lot: helmet, high vis jacket, shorts (knee-length with pockets). Usually obeys the lights, quick enough, some unpredictability when over-/under-taking. Most of these guys will weave to some extent, but not suicidally.  My tribe is probably one of the biggest, and it leads to lots of subtle negotiation at traffic lights - sizing each other up - checking the bike, the kit, the shoes - to decide whether or not to pull ahead or drop back.

But I mess with people's heads in summer by occasionally wearing a short skirt (with shorts underneath, I'm not out to cause accidents) and wedge sandals, and cycling at 20mph.

I hate to conform to expectations.

Comments

  1. Unknown9 May 2011 at 13:24

    you are hilarious. almost makes me want to dust off my bike.

    ReplyDelete
  2. Matjaž23 May 2011 at 21:53

    I am probably part of the second tribe, on point one and two, three is an occasional one.

    But really? 20 mph? That is around 32 kph, it is quite a speed. Do you mean average or top speed?

    ReplyDelete
  3. Trisha24 May 2011 at 08:32

    20mph is a a *slight* exaggeration. Even the cars don't get up to that speed in central London.

    ReplyDelete
  4. Anonymous3 August 2011 at 10:13

    My cousin recommended this blog and she was totally right keep up the fantastic work!

    Hi Vis Jackets

    ReplyDelete

Post a Comment

Comments have been disabled since this blog is no longer active.

Popular posts from this blog

Dissecting the Disruptor: What's so special about a ring buffer?

Image
Recently we open sourced the LMAX Disruptor , the key to what makes our exchange so fast.  Why did we open source it?  Well, we've realised that conventional wisdom around high performance programming is... a bit wrong. We've come up with a better, faster way to share data between threads, and it would be selfish not to share it with the world.  Plus it makes us look dead clever. On the site you can download a technical article explaining what the Disruptor is and why it's so clever and fast.  I even get a writing credit on it, which is gratifying when all I really did is insert commas and re-phrase sentences I didn't understand. However I find the whole thing a bit much to digest all at once, so I'm going to explain it in smaller pieces, as suits my  NADD audience. First up - the ring buffer.  Initially I was under the impression the Disruptor was just the ring buffer.  But I've come to realise that while this data structure is at the hea...
Read more

Dissecting the Disruptor: Writing to the ring buffer

Image
This is the missing piece in the end-to-end view of the Disruptor.  Brace yourselves, it's quite long.  But I decided to keep it in a single blog so you could have the context in one place. The important areas are: not wrapping the ring; informing the consumers; batching for producers; and how multiple producers work. ProducerBarriers The Disruptor code has interfaces and helper classes for the Consumer s, but there's no interface for your producer, the thing that writes to the ring buffer.  That's because nothing else needs to access your producer, only you need to know about it.  However, like the consuming side, a ProducerBarrier is created by the ring buffer and your producer will use this to write to it. Writing to the ring buffer involves a two-phase commit.  First, your producer has to claim the next slot on the buffer.  Then, when the producer has finished writing to the slot, it will call commit on the ProducerBarrier . So let's look at...
Read more

Dissecting the Disruptor: How do I read from the ring buffer?

Image
The next in the series of understanding the Disruptor pattern developed at LMAX . After the last post we all understand ring buffers and how awesome they are.  Unfortunately for you, I have not said anything about how to actually populate them or read from them when you're using the Disruptor. ConsumerBarriers and Consumers I'm going to approach this slightly backwards, because it's probably easier to understand in the long run.  Assuming that some magic has populated it: how do you read something from the ring buffer? (OK, I'm starting to regret using Paint/ Gimp .  Although it's an excellent excuse to purchase a graphics tablet if I do continue down this road.  Also UML gurus are probably cursing my name right now.) Your Consumer is the thread that wants to get something off the buffer.  It has access to a ConsumerBarrier , which is created by the RingBuffer and interacts with it on behalf of the Consumer .  While the ring buffer obviously n...
Read more