Tag Archives: LJC

Talking at a Conference

The fear of public speaking regularly comes in at number 1 in a top 10 of people’s biggest fears. It’s generally agreed that the idea of standing up in front of a group of people to give a talk is terrifying so you won’t judge me too harshly when I say that I was lightly cacking my pants when I went to the London Java Community Open Conference last week since I planned to be up on stage to give my first ever talk.

Unlike normal conferences where you have a schedule of speakers in advance, in an Open Conference anyone can put their name down for a talk. I decided that is something is worth doing then it’s worth doing twice by entering two talks: one 30 mins talk detailing my current team’s work as we rebuild a high volume website in Java (peaks of 30,000 executions in a minute and 88,000 http requests per SECOND! – slides) and one lightning talk of 5 minutes only to compare threads and actors for concurrency (slides).

Supplied with enough coffee and pastries to gird my loins, I put my name in for both and went in for the main kickoff session from Martijn Verburg and Ben Evans. As soon as that had finished I darted out to look at the schedule and saw what every first time speaker wants to see- I was first up!

Joking aside, this is perfect since you don’t end up sitting waiting for your turn and I bolted to my meeting room and got set up as quickly as I could. That I could welcome everyone in made me feel in control but with less than 5 minutes to go I only had way fewer people that I had hoped. Let’s face it, as a first time speaker you want to steer between the Scylla and Charybdis of too few and too many attendees. There’s no way I want to give my talk to the entire conference but likewise, I’d feel a little foolish giving it to only a couple of people.

Thankfully, the last couple of minutes before the start time saw the room fill up and I gave my talk to a full room of about 25 people. It may have been a bit of a cheat but the majority of this talk was based on the one given by Tim Morrow at Velocity EU so not only did I know the topic well but I had seen it been given by an experienced (and good!) speaker already. As soon as I got passed the first slide any nervousness had evaporated and I was off and running. I’d practised it a few times so timing the talk was not hard and the presenter view on powerpoint rocks since it gives you both the running time and your progress through your deck of slides. I was a little nervous about question time but since this was a case study on my own work I was on pretty safe ground.

My second talk was after lunch which meant that I had to sweat through that and the 3 speakers before me. That and the fact that this one was going to be to the full Five minute talks are simultaneously easy and hard – your time is too short to get into too much detail so you can focus on the area in hand (i.e. the bits you know!) but you have to have a perversely good understanding to explain your topic in only 5 minutes since you only have time for salient points. I was way more nervous for my lightning talk but again the waiting was far worse than actually standing up there and talking. Again, the questions were the hard bit and someone asked a great question that I didn’t know the answer to – “will Akka support Java in the future?”. What was cool was that the best way to answer this was to join up to the Akka user mailing list (something I have been meaning to do but never have) and ask and it doesn’t get much better when the Tech Lead and the CTO of the company behind Akka answer (“Abso-friggin-lutely, wouldn’t want it any other way.” according to the Tech Lead).

So how did it feel to finally give a talk? I felt far more involved that I ever had before. Yes people come up and talk to you afterwards and you end up chatting with other speakers whether you like it or not (and you do!) but the effort you put into your talk means that you are naturally interested in what everyone else is talking about and whether it affects your topic. The whole subject of the conference seems far more related to your own interests. It might be because you are interested enough in that topic to want to give a talk on part of it but I think that giving something back in this fashion creates an emotional bond that dispels any sense of imposter syndrome and just lets you enjoy the conference more. You don’t have to find a justification for just being there and you also learn far more.

So if you are thinking about giving a talk, all I can say is get stuck in and give it a go.

Writing a Technical Test..with a little help from the LJC

As someone who interviews developers, I had been looking at ways to improve our current interviewing process. I’m not a fan of written tests or of coding on white boards since they don’t accurately represent the day to day requirements of a developer and I don’t even think they are good surrogate markers.

Knowing Barry Cranford through the London Java Community, I thought I would ask him. Given that he probably sees more interview processes than anyone else I know it seemed a fair idea. After a quick chat over ice-creams (it was a hot day!) I suggested to Barry that I thought we should get potential candidates to do a small technical task before they came in so that we could go through it. That way I could get to see exactly how they coded and how they thought. Barry suggested we could improve it by building on it in a paired-programming exercise during the interview. That way we would be able to see how they worked in a team and in a pressurised environment.

I thought this was great and spend some time coming up with a task that could be completed within 1.5 hours but had some natural extension points for the paired programming exercise. The trouble was, I had no one to test it on other than myself and guys in my team. Again, the guys at the LJC came to rescue by volunteering to take it. I was pretty proud of the test and thought it was quite good as it allowed candidates to showcase their skills without being too hard but it was completely shredded by the reviewers! As one of the guys had pointed out, the task made too many assumptions about the domain knowledge of the candidate and the requirements were too vague for someone outside of the industry.

So I went back to work and rewrote it. The acceptance criteria became much tighter, I removed some of the ‘help’ than was actually misleading and reworded it so that the target goal was as clear as possible. The result is a solid task that is now being used for teams other than my own. So extra kudos for me and better candidates for the company.

Without the community input there is no chance that it would have been half as good. Worse still I would have been stuck with a bad test that I thought was good. I am very grateful for the various guys at the LJC for the time and effort they put in to help a fellow LJC member, so special thanks to Mustapha Hanafi, Martijn Verburg and most especially to Ged Byrne for all the help. Thanks guys.

Playing with JRebel

The London Java Community does more than a few cool things: meetups in the pub, coding dojos, training events, monthly draws and almost impossibly is run a a sane recruiter who actually knows how to deal with IT people. I throw my name into the hat for the prize draws every now and then and last month was my luck was in since I won a JRebel license (for those of you who don’t know JRebel allows the hot deploy of Java code changes and a load more).

Now not only is this a full license rather than being fobbed off with a time-limited trial but it also includes the Enteprise add-on. What makes it even better is that last week I was talking to one of the top techies at my current contract about using JRebel in a development environment so now I get to see exactly how it works. I’m all about the value added 🙂

Come back for an update in the next few weeks.