Let's start with 2 new articles over on the jOOQ blog – the first is a deep dive on using lambdas for database access, and the second – a look at the new Optional semantics in Java 8:
As Java 8 is out and about, we're going to see a good few articles about how it affects the way we write code going forward. This is one of these articles, and it's a good one:
Very useful post for the advanced Mockito user:
Eclipse has finally came out with the official Java 8 support – took a while to get here, but it looks good:
Next – good things come in pairs – and this week we have a couple of great testing articles about working with Spring and WebDriver and HtmlUnit. Very helpful if you're doing any kind of UI testing (let's assume you are).
And finally, a foray into the Enterprise space, where Spring is well represented – and an early look at how Java 8 will affect that landscape:
The third part of the excellent series about tracking errors in a Spring app is out, and of course it is makes it into this weeks review:
And finally, a great 6 part series about building a RESTful API with Spring:
=> Versioned, Validated and Secured REST Services with Spring 4.0 (Part 1: Creating the Basic Application)
Nearly every week, one thing keeps me engaged more than most other stuff I read – and this week, it's the continuation of an article from last week – TDDing a chess game.
A few years back, before I gave TDD a proper go and decide to work though the initial pain, I had tried it a few times only to revert back because I couldn't really make it stick. That seems to be the case with a lot of people – you somehow understand that TDD is an important practice, you may even get that it's one of those rare things that's going to change the way you code irrevocably for the best – but you still don't pull the trigger.
For me, pulling the trigger was a 3 day retreat with J. B. Rainsberger and Corey Hanes – I forced myself to jump to TDD because I saw what it could do. A video series like this – solving a real problem with TDD is important – so I'm excited to follow this one as it unfolds:
Couple of interesting articles about a good interview questions – some really nice points in here for anyone on the giving end of the interview process:
By Martin Fowler – is this the definitive word on what an Enterprise Application is? Probably.
And finally, a fun little 10 minute demo of using Google Docs as a testing environment, by J. B. Rainsberger – always teaching:
Unless you're one of the lucky souls that has been unlikely fortunate – you probably had to sit through your fair share of go-nowhere meetings, and you'll find this piece especially relatable: