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

TradeTech 2011 - Not like a developer conference

I attended TradeTech last week, an annual event about Equities and Derivatives trading. I assumed from the title that there would be a reasonable focus on technology, but I found it was more “Trade” and less “Tech”.

The fascinating thing to me was how different this is from the sorts of technology conferences I've been to. For example, I popped into JAX this week (albeit in the evening for drinks). At technology conferences (<gross-generalisation>) people tend to subscribe to a variety of dress codes and fashion clans, usually from jeans through the range of business casual, including your fair share of goths and alternatives. Suits would be unusual (</gross-generalisation>). At this place, people were scarily conformist. A few years back, the suits at least would be different colours – navy, greys and black – and may or may not include pin stripes. On Thuresday, almost everyone was wearing a particular shade of tasteful dark grey.

I was also pretty shocked at the time people snuck off to go to the pub. Don't get me wrong, I'm all in favour of imbibing alcoholic beverages as frequently as possible.  And I prefer networking in the pub to poncing around in some conference centre. But I feel it's Bad Form, and I was surprised (and a little bit jealous) that it seemed to be the norm. I felt for all of the later presenters.

Still, I showed my support for them and I turned up to some actual presentations.  The most interesting ones to me were Baroness Eliza Manningham-Buller talking about her time as head of MI5, and Richard Peterson going Inside the Trader's Brain.

The Baroness was talking about leadership during times of crisis – she was in charge shortly after 9/11. What I found interesting, and resonated with me, was her focus on her people. An intelligence organisation is all about the people who work for it. She stressed that it was important to bring fun into the work place, especially because it was a particularly traumatic period to be working. She instigated family days and helped the employees show their families what it was they did. I'm not quite sure how much they could show, given the nature of that industry. But I liked that she understood the people were more than just minions, workers in a hive, that they had families and that they wanted to be proud of their work and share it with the significant people in their lives.

She also refused to take credit for anything for herself, but talked about her team, about the people around her and in the organisation. I like leaders who recognise that it's not all about them.

The thing that stuck with me the most is she said that leaders who take themselves too seriously are not taken seriously by their underlings.

Richard Peterson's presentation was about the risk-taking and risk-avoidance areas of the brain. He showed how your risk-taking behaviour is influenced by bias, and how subtle it is. There was a lot of interesting stuff in this, which scratches my random-interest-in-psychology itch, and confirms what I've been reading/hearing about how behaviour can be triggered and changed.

Ultimately he gave some advice for how to reduce the impact the rest of the world might have on your trading strategy, which is applicable to all of us:
  1. Maintain healthy routines
  2. Take time to reflect daily
  3. Letting go
  4. Gratitude
The ulterior motive for me to be at TradeTech was to watch my boss's “How To Do 100,000 Transactions Per Second At Less Than 1 Millisecond Latency?” presentation. This was a cut-down and updated version of the one he and Mike gave at QCon last year. If you are at all interested in concurrency, high performance, or programming generally, it's well worth the hour to watch it. It outlines the architecture we use at LMAX to get very high performance from our exchange without using anything particularly special in terms of hardware. All it takes is good design and something Martin calls mechanical sympathy.

Anyway enough corporate plugging.

Overall I came back from TradeTech with lots of ideas of things I wanted to do at work and ways to help us market the platform in future. I also came back with a certain cynicism for these types of very vendor-heavy events. However, I did meet some interesting people, and it was a different crowd to my usual technical comfort zone.

 And it did get me thinking, which is really all these things should do.

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