- Understand how to improve performance with your Java code using Java 8 language features.
- Learn hands on techniques to discover and implement common Java 8 refactorings.
- Understand when you should and should not apply key refactorings in Java 8.
While the list in the talks section of my blog covers past presentations, this page should list my confirmed upcoming events.
Last night was the final get-together to discuss the Java 8 MOOC. Any event hosted in August in a city that is regularly over 40°C is going to face challenges, so it was great that we had attendees from earlier sessions plus new people too.
As I mentioned last week, the Sevilla Java User Group is working towards completing the Java 8 MOOC on lambdas and streams. We’re running three sessions to share knowledge between people who are doing the course.
I wrote a post for the JetBrains Upsource blog about some of the things you should be looking for when you do code reviews (and some of the things you should not be looking at).
Daniel Bryant and I did a keynote at Devoxx UK about how individuals can add something to a team to make the team more productive, and overall more awesome.
The Sevilla Java User Group is working together towards completing the Java 8 MOOC on lambdas and streams. As part of this, we’re running three sessions during the course so we can, as a group, ask questions about the lectures, get help with the homework, and (if we’re feeling very smart!) help people who may be struggling (or might not have watched the videos).
While I was at QCon New York (probably my business conference this year!) I was interviewed by Ralph Winzinger for InfoQ. It felt like a short interview at the time, but we covered a lot of ground - Java 8, Java vs other JVM languages, the effectiveness of the JCP, and the future of Java.
Video and the transcript are available on InfoQ.
So, I get asked a lot about how I got into technical advocacy / evangelism1, so it seems like the most cost-effective way to answer this question is to write a post about it. Warning: it’s a long one!
This presentation is about how to change a team’s attitude towards writing automated tests. The talk covers the same case study as Groovy vs Java for Testing, adopting Spock in MongoDB, but this is a more process/agile/people perspective, not a technical look at the merits of one language over another.