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

Brain Overload!

The moral of today's story - be careful what you wish for.









This is my brain






During the normal course of my life, it's filled with Stuff.







Early in November, 10gen ordered me to go to New York to learn about MongoDB (Oh No!  My Life Is So Hard!).  I was looking forward to shopping and taking photos of the devastation wrought by Sandy, but actually I spent the whole time drinking from the firehose of MongoDB information provided by my ridiculously smart, ridiculously well-informed colleagues.

(I didn't even buy shoes!  But I did buy a new winter coat, so there is some balance in the world).



24 hours after landing back in in London, I was on a train on my way to Antwerp for Devoxx.  There, I did three talks, including a new talk on Agile, co-presented with a colleague from LMAX (a teeny snippet of which can be seen in the video on the Devoxx home page).  Running from thing to thing, helping out at the 10gen stand and meeting new people and those I count as friends kept me pretty busy (did I mention My Life Is So Hard?).









...and now I'm at Skillsmatter Scala Exchange, writing a blog post instead of listening to the talks. Because I've got no more space in my brain for anything, let alone a new language I haven't studied at all (don't tell anyone).






Fortunately I'm not travelling again for the rest of the year, so I'm hoping to start doing some Actual Code some time soon.  I have one last conference, the LJC Open Conference this Saturday, which fortunately is on home ground.  If I can get away with it, I'll go and watch other people talk rather than perform myself.  For any LJC guys reading, you can submit talks in advance, or suggest topics you want to see.

(This blog post was brought to you by a person who had an iPad, a stylus, and a desire to procrastinate against doing important stuff like reporting her stolen bike to the insurance company)

Comments

  1. javapapo20 November 2012 at 19:55

    Hi, I saw 2 of your talks @Devoxx ! Keep them coming i think you have a natural talent on presenting. Happy coding :)

    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