Less than a day now, and I'll be leaving for London - my flight leaves Tuesday morning, and arrives in London Tuesday night. If it's like the last QCon, it'll be energetic, interesting, very tiring, but completely worth it. I'm looking forward to it!
If you are there, come and say hi - I'll probably be in the Wordsworth room the whole time. :)
I went ahead and published the QCon Interview schedule on a Google Calendar. Enjoy!
It's just over two weeks until the interviews start at QCon London, and everything is set! We've added the interviews to the official website, and you can see the Wednesday, Thursday and Friday interviews there. As a note, there are actually two more interviews on Thursday which are not listed on the schedule - there is an interview with Neal Gafter at 18:45, and with Linda Rising at 20:00 on Thursday. A Google Calendar containing all of the interviews is also possible, if there is interest in it.
To give you an idea of what might be happening, I wanted to share this little gem from the last QCon London. It's quite a good laugh, especially for those that have seen the Ali G show:
It's less than a month now to QCon London, and plans are rushing to completion. I'm in charge of coordinating the interviews this time, and we've got a lot of good ones lined up. Not only that, but the interviews are now going to be accessible to conference attendees - if you are at QCon, you can sit in on the interviews and participate - I and the other interviewers will be getting questions from the audience that we will ask the interviewee, so this is your chance to get those burning questions you've always had answered.
We expect shortly to have the entire list of interviews and times posted on the QCon website, but to whet your appetites a few of the people who will be interviewed are (in alphabetical order):
There will be 17 interviews in all, so these are just some of the people you will have the chance to ask questions of. I hope to see you there, and bring your questions!
When I was at QCon San Francisco last week, Martin Fowler put together a panel of 4 people that had been speakers at the conference. They accepted questions from the crowd, and I asked a question about the future of software development given recent changes in parallelism. I want to ask that same question here (with a little bit of preliminary set-up first).
There is general consensus that the current set of programming languages and paradigms is not well suited to concurrent/parallel programming - almost all of these languages were created with sequential, single-threaded development in mind. Given that it is now almost impossible to get a single-core CPU, and that the number of cores on a computer is going to keep expanding dramatically, we need to do something to address this pain point.
There seem to be four major things that we can change to address the parallelism/concurrency problem:
Which do you think is the most likely to succeed, and why?
