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

JavaOne: The Summary


So, JavaOne.

Taylor Street Cafe
I'm going to be controversial.  I think this was my favourite conference of this year.  I know that's not trendy, and that Oracle-bashing is still a popular pastime.  And I know I've also made a big deal about how much fun it is to meet people who program in different languages.  But there is something very special about being surrounded by thousands of people from all around the world who use the same technology as you, some facing the same problems, some solving very different issues.

Maybe it's because since I first spoke at JavaOne last year I've met a lot of people in this ecosystem - Oracle Java people, other conference organisers, Java User Group leaders, speakers and attendees from all sorts of places - and seeing many of them in one place is fun and makes you feel like you're "home".  I'd be sat in the Taylor St Cafe area and people would sit down and hang out with me.  I'd be hiding somewhere trying to write a presentation and people would say Hi.  I'd be separated from the other LJC guys while I grabbed a glass of water and someone would stop to chat.  It was awesome.  I even managed to get a tiny bit of work done between socialising.

Personally, I have learnt very valuable lessons:

  1. Doing two conferences back to back is exhausting.  If I do it ever again, I really need to optimise my travel between them (i.e. not fly from St Louis to London and then to San Francisco 48 hours later).
  2. Especially if I have two conferences back to back, but almost definitely as a rule, it's best to have the materials for presentations complete before the conference.  I probably would have enjoyed myself even more, and definitely had a chance to see a lot more sessions, if I hadn't had one presentation to finish.
  3. Presenting four sessions in one conference is extremely challenging.  Technically I only had two full-length presentations (the Disruptor presentation I've done at OSCON/GOTO/QCon etc and my Technical Approach to Women, which was more like a very structured BOF), a short 20-minute talk and a panel.  But I think one full-length presentation and a couple of other bits is probably a much more sane amount.  Especially given 1) and 2) above.
So I didn't get a chance to really see many sessions.  I'm sure the blogosphere will be full of good summaries of them, and they will be available for free via the schedule builder (audio and slides only).

There will be a bunch of other blog posts mentioning the inconvenience of having it in three hotels, the poor suitability of some of the rooms, the difficulty of sharing San Francisco with Oracle Open World, the mediocre food.  But you don't spend the money to fly halfway across the world to San Francisco for the crappy box lunches.  You fly here to meet - face-to-face - some of the people who created Java, those who are steering it now, and the community that continues to make it relevant and fun.

Highlights for me:
James Gosling talks about Robots!

I already mentioned the technical keynote in my summary of Sunday, but I forgot to talk about Dr Robert Ballard's section, which is crazy because it was so inspiring.  What I got out of that was how much fun technology can be, and how kids are really ready to be amazed and engaged with science and technology, provided you get them young enough.  I also really loved that the photos of all the scientists showed great diversity, something he seems to take very seriously.  His comment was "A child needs to see their face 20 years out to know they can play in the game. Don't sell science, sell scientists and engineers".  The point I took from that was that by focussing on "science" and "technology", we could be losing people - by showcasing the people, the talent, the passions, we are much more likely to engage children.  And I think that stands for adults as well.

A robot!
And this nicely fits the message I was trying to get across in my session on Wednesday (which I know I've already blogged about) - it's dead important to address the failure points when it comes to diversity, but I think we forget to push the positives - the reason we don't understand why some groups of people are under-represented in technology is because we all love being here, it's a great industry to work in.  I'd love to see our passions more widely showcased than simply at conferences where we're a self-selecting audience.

The LJC panel about our involvement in the Java Community Process
Not only was this a great JavaOne for me personally, it was a real triumph for the London Java Community.  Last year there were only two of us here, and Martijn was working hard to introduce me to the other JUG leaders and the people on the JCP committee that we were going to be working with over the next 12 months.  This year, there were five of us here, spreading the word about our work as a member of the Executive Committee of the Java Community Process (the Java standards body), primarily our Adopt a JSR program.  We also wanted to talk to a load of people about the Adopt OpenJDK program as well, we've found lots of developers are really keen to develop the language itself, Java at the fundamental level, and we really want to help bridge the gap between the guys who work on the OpenJDK project and the developers in the community.  But all our hard work over the last year, kicking off these programs and working with other user groups and Oracle to really harness the power of the community, has been recognised.  We've won not one, but two awards - woohoo!  Fame, glory, girls/boys, money etc await us!  Well, not quite... but it's certainly nice to be the "Award Winning London Java Community".  

The LJC in the Community Keynote
Our two shiny accolades are:
So, a really great JavaOne.  I'm not sure, if I'm honest, who reads my summaries of conferences - I know lots of people do read them, but I don't know if that's those who went to the conference or those who would have liked to have gone, or those who don't know what it's like at conferences.

But in case this is useful to anyone who is reading this, next year come to JavaOne if:
  1. You want to know what's coming up for Java the platform or Java the language
  2. You want to meet, or at least see presenting, the people who are actually making these changes
  3. You want to meet other Java developers from around the world - whether you want to find someone with the same problems as you, or want to see different issues that face people.
  4. You want to see the Power Of User Groups!
  5. You want to understand how decisions are made with regards to the future of Java
  6. You want to meet like-minded people
The Exhibitors Hall was like Vegas! But there was a buzz which was infectious
Oh there's millions more, and even if you only tick one of those reasons, I personally think it's a great way to get a better understanding of the language we use every day as developers.

And finally, some of my sessions will be available, audio and slides only, via the content catalog.  Look for the following:

  • UGF10467 - Benefits of Open Source
  • CON3732 - Concurrent Programming with the Disruptor
  • CON5130 - London Java Community: How to Change the World
  • CON11338 - The Problem with Women: A Technical Approach


Comments

  1. laker20006 October 2012 at 18:11

    I could not make it this year. So thanks for posting; very informative. See you there next year.

    ReplyDelete
  2. Hildeberto Mendonca8 October 2012 at 02:49

    i think it would be a good idea to move JavaOne to Las Vegas in 2013! \o/

    ReplyDelete
    Replies
    1. Trisha8 October 2012 at 09:37

      While I think Vegas would be awesome, I can't really see Oracle going for it...
      a) The city's reputation will put off swathes of people from coming
      b) I can't see companies being happy to pay for their developers to spend a week in Sin City.

      But if I get invited to a conference in Vegas I'll totally be there!

      Delete
  3. thatguylionel9 October 2012 at 06:13

    The CON3732 session was very informative and will definitely look into it more attentively, as I've seen loads of areas in our current work space where the disruptor can be implemented into . Thank you very much for the presentation.

    ReplyDelete
    Replies
    1. Trisha9 October 2012 at 10:06

      Thank you, good feedback is always appreciated!

      Delete
  4. indiawins2 November 2012 at 10:04

    This comment has been removed by a blog administrator.

    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