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.
YOW recorded me, yet again, talking about the adventure that is the design of the new Java Driver for MongoDB. This is the same talk I gave at GeeCON and DevoxxUK, with some updates based on our Journey So Far. In it, I cover the architecture of the new driver and some of our current thoughts around where we want the API to go.
Since I have a tendency to bang on every now and again about how we, as developers, could do better in managing our careers (for example, by creating CVs that don't suck, and by staying ahead of the curve), Dave Thomas asked me to speak for a mere 50 minutes on the subject at GOTO Aarhus, a talk I wasn't enormously happy with as there was no way to cover a lifetime of hard-fought experience in such a short time. Dave seemed to like something in it though, as he gave me the opportunity to present the topic again at YOW last December, and this time I think I managed to distill the important points into the (still ridiculously short) time allotted.
See the video here, and please give me any feedback you have.
I recognise there are many many more topics I could cover, so I'd better start making a list. Suggestions?
If you see anything about LMAX - the Disruptor, Continuous Delivery, or even the selection criteria for hiring developers, you'll see that LMAX is pretty keen on Agile. However, no-one's documented the Agile process there, as far as I know. Although I personally had it on my todo list, I never had the motivation, the hook to do it. And I realised eventually that's because I'm not sure it's a process that would work very well for another team, in another company, working in another business.
Yesterday dawned, with a sense of foreboding (actually it dawned with me coughing my lungs out, but we've heard enough about the sub-optimal state of my respiratory system this week). On this day, I was giving the talk I was dreading when I got asked to do it. It's the talk I actually put more work into than any of the other sessions I was presenting at this JavaOne. It was the Women In IT talk.
Here's a video of my Open Conference session on the business benefits of open sourcing your software. Given that the conference was at a weekend and had a very intimate feel, I think I was a teeny bit more honest than I usually am. Enjoy.
A few weeks ago, I presented my new "User's Guide to the Disruptor" talk to the London Java Community. Since it was very kindly hosted at Skillsmatter, there is a video of the presentation available, and the slides are below.
At JAX London Mike and I presented "Understanding the Disruptor - A Beginner's Guide to Hardcore Concurrency".
This is the session we initially previewed to the
London Java Community a few weeks earlier. The content is the same, but the feel of the presentation was quite different to us - the
venue for the LJC event was more intimate, and it was easier to interact with the audience. At JAX, we were up on stage,
which was pretty cool actually, but meant that it felt more like a lecture and it was less easy to connect with the audience.