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

A NYSE Product Manager and an LMAX Developer walk into a low latency trading seminar...

"What... exactly... were you guys looking to get out of today's event? Because..."

"Because we're girls?"

"Um... yes..."

Kim impetuously opts for The Truth: "We're here to meet men."

Our interrogator looks round dubiously.

"No, really, why are you here?"

Phew.  My reputation is intact1

Kim eloquently describes what her situation is as Product Manager and the criteria she's measuring third party products against.  I explain how LMAX aims to be the fastest retail exchange in the world, and therefore low latency is a tiny bit important to us.  I talk about how we created The Disruptor on our path to achieve that goal.  The guys gathered around us look a little... shell-shocked.

I'm exaggerating for Dramatic Effect.  Before anyone starts getting upset about the only two girls at the event who weren't staff or hospitality being singled out, you have to give the guys credit.  They approached us, engaged us in conversation, and had a very serious question about what we were after, and was there anything the vendor could do to either improve their offering or to make their sales pitch more appealing.

And don't get me wrong - it's brilliant being different in a situation like that, if people are brave / foolish / drunk enough to talk to you.  It beats the hell out of sitting in a corner trying to get up the nerve to speak to Strangers (been there, done that).

But it is quite a contrast, even from the Java events (JAX London, Java One).  There, I was in a select group of people of the female persuasion.  But I was also part of a community, and treated as A Developer.  At very specialised events (low latency, high performance in particular) diversity is almost non-existent.  You can count the number of women on one hand (if you can see any at all) and even the developers wear suits (poor bastards).  However it would probably be better if you could hide your surprise at hearing technical terminology coming out of a woman's mouth.

But... I kinda like it.  Yes, I'm an alien.  Yes, I'm special.  But if it means you make the extra effort to speak to me, I can live with that.


1 "Extra extra, read all about it! Blogger And International Conference Speaker Only Does It To Meet Boys!"  Not quite Jordan Stalks Rugby Ace For Sperm Donor.  Which I really did see this morning.

EDIT: oh yes, and of course I forgot to plug my panel at Devoxx next week: "Why we shouldn't target women"

Comments

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