The fantastic thing about an open conference is that a) you don't have to prepare like mad for it and b) the short sessions and wide variety of subjects mean that you learn stuff you didn't expect to.
Given how much I've been presenting lately, and with the conferences piling on top of each other back-to-back leaving little time for preparation, I had decided not to speak at the open conference, but to sit and learn for a change - it's a great opportunity for new speakers to present for a start. But that resolution lasted all of 3.54 milliseconds. After all, if people don't like the sessions I propose, they won't come, so I lose nothing by suggesting some.
|Photo by Ged Byrne|
Next, I was roped into a Java Performance panel, with the JClarity guys (Ben, Richard and John). I was surprised to see that not many in the audience were working on low latency systems - in London you'll frequently find a room full of Java developers who are all working in finance on things that have specific performance requirements. It was good that we had a this variety of developers, because it meant we covered a much broader range of subjects, and could discuss what to think about and where to get started when you're considering your non-functional requirements.
Immediately after that I was on another panel, with some of the same suspects, talking about the LJC's involvement in the Java Community Process and the Open JDK. I really like these sessions because it's easy for us, who are dealing with these things at least on a weekly basis, to forget that most of our members aren't familiar with either of these two things. What's encouraging though is that after just a short introduction to what they are and how we can impact them, most people want to be involved in some way. The hack days are particularly appealing to developers (not surprising). Although we've had a number of very successful hack days, we still need to work out a way to scale them - how do we attract more people? How do we make the best use of their time? In particular, we need to work out how to cater for people with different timetables (weekends vs evenings vs week days), and how to handle the split between beginners and those who have already been to at least one hack day. I'm excited about what we've achieved so far with the hack days, but I think there's so much more that can be done.
|You can't tell from this photo, but there were girls this year|
Next up, I gave an intro to NoSQL From Devoxx, it was clear that while a lot of developers have heard of the NoSQL movement, and of databases like MongoDB, it's not clear to them why you'd chose these over traditional databases. Which is a relief to me, because that's exactly where I was three months ago. So this was a really quick (30 minute) overview of the different flavours of NoSQL, what they're good for and why you might pick one over another. Obviously there was a focus on MongoDB, since this is the one I know most about, but I also covered the strengths of some of the others. I really enjoyed giving this session - the audience was perfect for the topic, the questions were intelligent and drove the direction of the discussion, and I had a number of positive comments from people who felt like they had learnt something.
I gave another session which was a recap of the JavaOne and Devoxx "Problem with Women" talk, but even shorter. The fantastic thing about this was the energy from the people in the room - these guys like what they do and they're keen to tell other people how great it is to work as a developer.
how to write their CVs, how to stand out from the crowd, how to network to increase their chances of finding a good job, but they need to know to start looking for these resources. Worse, though, is the problem of the employers - if you're a big company you have a non-technical HR department standing between the team needing a developer and the candidates themselves, and smaller companies don't have the time to invest in the hiring process, or going out and networking to meet people at things like LJC events. It's a tough problem, and one I'm extremely interested in. I'm hoping that the "Attracting Great People" track I'm running at QCon London will look at some of these issues, and give some advice from those who are doing a good job.
The last session was an exploration of all that is wrong with Agile, led by Ged Byrne. It was an interesting discussion, the only disappointing thing about it was that everyone agreed with each other! Certifications Are Meaningless; external Agile coaches and consultants aren't necessarily invested in improving your business; a formal Agile process is really defeating the point; and, most importantly, let's try to remember the original agile manifesto.
In summary, it was a really great day! I enjoyed it as much as I enjoyed last year's, for many of the same reasons - we have a fantastic community, it's a great event for meeting people, it's brilliant for encouraging new speakers, and if you are speaking you get much better feedback than you do at the large events, because you can involve your audience directly and give them what they really want. I can't believe how much I personally have achieved since my first solo talk at the LJC Open Conference last year, and I can't wait to see what the next year holds.
(More photos from Andrew Black)