After a long (yet exhilarating) week the final day started with two keynotes, almost as if Oracle somehow knew that people may not have had much sleep the night before 😉
With the previous two days of JavaOne 2013 now past us, it was time to get a little more practical and look more closely at some concepts introduced earlier in the week. Today wasn’t going to run as late into the evening as previous days since Oracle had their appreciation event beginning at 7pm. Personally, I was looking forward to the shorter day, getting a break from ‘conference brain’ and getting some time to consolidate what I had already picked up this week.
Day Two of JavaOne was another huge day and the longest of the entire week, finishing 9.15pm. Looking back over it, it was the strongest technically featuring excellent presenters and ideas. The morning began with some sessions on best practises in functional programming and cloud. The rest of the day was all about polyglot JVM languages. I could not be more proud that the JavaOne organisers have enabled this awakening. Talking to past attendees, much more of the conference schedule has been dedicated to emerging languages this year.
I’ve been lucky enough to be in San Francisco this week to cover the JavaOne conference. Today (Monday 23rd) was the first real day of conference proceedings and it was a very full day. Sessions started 8.30am and ran until 8.15pm with usually half an hour to an hour break in between. In this post I’ll focus on the best sessions of today as well as some of the logistics of being an attendee at a big conference.
The 18th JavaOne started this Sunday in San Francisco. Covering three hotels in downtown SF, Hilton, Parc55 and Nikkon and with keynotes in the Moscone Centre, Oracle OpenWorld is hands down the biggest conference I’ve ever attended. It covers 5 days in total and over 500 sessions plus side exhibitions and events. And it certainly needs the room, not only to accommodate the number of attendees going to these sessions but the breadth of the platform itself.
In September I flew from my home in Melbourne, Australia all the way to Crete in Greece for the Java Specialists Symposium 2012. It’s an open spaces ‘unconference’ which unlike a regular conference has no set program. The schedule is formed by the attendees when the conference begins. Attendees volunteer to present topics, convene discussions and organise coding sessions. Three sessions run each morning with the afternoon left to hack, code and otherwise enjoy the sunny surrounds that Crete has to offer that time of year. In this post I’ll talk about my experiences at this unusual conference on the other side of the world.
YOW! 2012 took place a few weeks ago, bringing some of the world’s best developers and agile gurus on a roadshow across Melbourne, Brisbane and Sydney. Having been to YOW! in 2010 and followed the line-up last year, I can say the conference undoubtedly continues to improve each year. In this blog I will talk about my overall impressions of the conference, and a couple of the more interesting things that stood out to me.
This post is about unit testing with Groovy. Groovy was the first language I used after Java. It lets me do a lot of the things I do with Java, but more quickly. Like many developers who are using another language after Java for the first time – whether it be Ruby, Scala, Groovy or something else – I’ve quickly come to love it.
In this post I’m going to show you how Groovy can make your tests more succinct. We’ll focus on syntax sugar for creating and consuming Maps and Lists, which is something you do a lot of when preparing data for a unit test. Than I’ll give a quick introduction to closures, which will lead us into some of the techniques we can use for mocking in Groovy.