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

GOTO Amsterdam

Three airports and three hotels in a week, and I don't know whether I'm coming or going.  Add to that a mere four hours sleep last night, and this might resemble the ramblings of a mad woman (more than usual that is).

GOTO Amsterdam was a different affair to GOTO Copenhagen, which is not necessarily a bad thing - it's great that the events have their own personalities and aren't cookie cutter versions of the same thing.

Great communal area for meeting people, in a unique venue
Amsterdam was smaller and shorter, and therefore felt even more intimate than Copenhagen, which didn't exactly feel massive either.  The venue was beautiful and imposing (and not at all air conditioned!), which I think also contributed to its unique feeling; the timetable felt less intense (although both conferences had a reminder that the next session was going to start, great for moving people at the right times); there was a different mix of attendees and speakers (fewer Danes and more Dutch for a start); and the coffee was marginally better in Amsterdam.

Both conferences were very friendly, but Amsterdam felt even friendlier - possibly because it was smaller, or maybe it was me because I was already in the Conference Zone, but people were coming up to chat to me from the very first minute, which is great for a shy person like me...

The Java Track
Anton Keks demonstrating simplicity in Java
I was very pleased to see Anton Keks kick off the Java track with a talk to pull us developers back to reality.  Instead of running off to find a shiny new language to fix our problems, we can toss away overblown frameworks and enterprise architecture and write nice, simple Java.  We can even go against basic conventions to make our code more terse and readable.  While I'm not sold on all suggestions (e.g. not using curly braces for single-line if statements) I'm totally behind the theory, and it led nicely into my Disruptor presentation.

At Amsterdam, rather than being relegated to a smaller room up a lot of stairs, my Disruptor talk was in the main, grand hall. This is not always a Good Thing, because standing on a large stage tends to separate you from the audience, and one of the things I like to do is have a lot of questions and interaction from the audience.  I think I pulled it off better than I have in the past, just because I was aware of the problem.  I even forced some of the audience to move from the back to closer to the front to give the illusion of intimacy - I totally didn't expect hat to work!  The session went really well and I got good feedback - it might actually have gone better than in Copenhagen, but I think having given the same presentation the previous day probably helped.  And although I like having it videoed so more people get a chance to look at it, it's nice when it isn't - you don't feel the pressure of having mistakes immortalised and replayed infinitely.

Agile
I missed all of the Agile stuff at Copenhagen, so I tried to make up for it in Amsterdam.  Interestingly I felt like I saw things from two different types of practitioners.  

Firstly, you get the war stories of trying to fit agile into an organisation that isn't used to working that way - conferences have been showcasing these for quite a few years now, and it's still really important to continue showing the different types of obstacles and how to overcome them (and why - the benefits you get when it starts to work).  What's different I think is the types of company that are now trying out agile are the sorts of organisation that never would have used it in the past, because it appeared too unstructured and not rigorous enough.  I think this is a good sign of the increasing maturity of agile and its acceptance into common practice.

The other types of practitioners are those who've set up their whole organisation on Agile principals, from the ground up.  These companies are waaaaay ahead of what you read in books, and have problems that are really only just starting to be talked about as these companies grow up and scale up.  LMAX falls into this category, but I was both surprised and pleased to see other organisations doing similar things to us and facing some similar challenges - in the past I felt that we were alone with no-one to learn from, but it seems I was wrong in that.  I've now got a few ideas I want to take back with me that are certainly worth discussing back at the mothership.

Keynotes
The Lego Keynote was interesting, it's fascinating to see how another industry works to balance creativity and constraints (costs, lack of manual dexterity in small children, marketing/branding guidelines etc).  I'm still mad at them because of the horrible Lego Friends thing aimed at girls, but I did come out of that thinking I really really want to work for them.  Not sure it actually helped me in my day job….

The keynote taking lessons out of Zen and the Art of Motorcycle Maintenance was quite thought provoking.  The main things I remember were around combating frustration and boredom - we need to create working environments which allow you to step away from a problem and come back ready to face it again.  And we need to allow ourselves to do this.  

Multiple sessions, including this one, talked about flow - how when you're in the zone (as a developer) you can be creative and productive.  Creating environments and processes that not only enable flow but encourage it is going get the most out of your developers.  As a bonus, it's going to attract other great developers to join you.



So, after the end of a long week…
Despite the extreme tiredness, the unexpected heat and unwelcome hay fever, I'm feeling pretty creative and full of ideas right now.  I've thought of quite a few things I'd like to present on - more fluffy things than just the Disruptor - and I've got some projects I'd love to work on.

I really hope that survives past moving apartment (today - argh!) and going back to work.  Events like these are designed to make you think and to try and help the industry move forward, it would be a shame to lose that momentum in the every humdrum details of life and work.

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