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

OSCON Day One

So, my first day at my very first OSCON.  I have to say that when Ben and Martijn told me I had to do OSCON, that it was one of the conferences to go to, I was sceptical - not because I thought it would be rubbish, but because I have enjoyed all the conferences I've been to for different reasons.

But I'm really impressed so far.

The program is packed with great topics and speakers, and so many things I want to see that clash with each other.  It's frustrating, and all the sessions get in the way of all that networking stuff!

The people are so friendly.  They smile at you randomly in the corridor.  They talk to you for no reason.  As a Londoner it comes as a bit of a shock to the system.  And it's nice!  Great conversations with different people.

The venue is set up for these encounters with plenty of places to sit with the laptop or mingle or meet and sit with people at lunchtime.

The exhibition area is not a total waste of time!  The booths are full of educated people not selling me "solutions" that I have no power to implement in my company, but engaging me in conversation about things that interest me as a developer.  Many of these are even useful for my day job - who knew!

Some of the sessions are being streamed so if you're not here, I highly recommend that - from what I've seen so far the quality of the video is good and it's the next best thing to actually being here.

I'm inspired, actually.  It's clear to me that Open Source is key to our industry.  Not just because of the technologies that have been created that help power some of our most successful companies.  But because with only the love of the thing you're doing to motivate the developers, community / cooperation / people / soft-fluffy-stuff is fundamental to success.  Talks here have highlighted to me that there are lessons that money-making companies can learn from this community around how to motivate your developers.  There are even lessons I have learnt today around how to improve relationships in my personal life.

Why isn't this community the poster child for our industry?  Why isn't this the entry point for everyone interested in development?  I know we say (even I've said it myself) that contributing to a project is a great way to advance your career, especially if you're junior.  But we can also showcase some of the really interesting stuff about being a developer by using the open source community - communication, cooperation, and working on cool stuff.

Why is it that even within our industry, the open source community is seen as being niche, and difficult to get into?

Comments

  1. Anonymous9 August 2012 at 22:01

    "Why is it that even within our industry, the open source community is seen as being niche, and difficult to get into?"

    Is it? I'm not so sure. In which way would it be a niche?
    And believe it's rather easy to get into open souce - assuming by getting into you mean becoming involved with a project. You participate actively on the mailing list, you supply patches and sooner or later you'll be a commiter.

    Phuhhh, I envy you for all the conferences you (can) go to B-)

    ReplyDelete
    Replies
    1. Trisha10 August 2012 at 13:53

      Well... it's entirely possible that it's my ignorance, but the for the first 10 years of my career I saw open source as being something hard to get into that needed you to be really good, or really interested. Even if you work in places where programming is not "just a job", it's not that common that you'll be encouraged to join an open source project by your friends and colleagues. It is more common within user groups, but it's surprising how many enthusiastic developers aren't even aware of the existence of user groups.

      Just my 2p's worth.

      And yes, I am lucky to go to a bunch of conferences - I definitely don't take it for granted yet! It's worth the trauma of standing up and talking to people just to get to experience the conference.

      Delete

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 heart of the patte
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 the first bi
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 needs a se
Read more