Another week, another good set of articles.
There have been a lot of articles this week, and in the interest of keeping the weekly review short as well as actually valuable, I had to make some touch choices.
This series is consistently putting out great stuff – even if you don't use jOOQ it's worth reading to see how Java 8 is going to make APIs a lot better.
This is a good writeup answering the now – age-old problem of how to best test private methods. Nice.
Nice in-depth article about the new Date-Time API that's going to be out soon with Java 8. This is a bit more than a week old, but I wanted to include it anyways.
Spring Data is making headway this week (I'm most excited about the new pagination support):
- => What's new in Spring Data Codd RC1?
- => Spring Data Elasticsearch 1.0 M1 released
- => Spring Data Couchbase 1.0 RC1 released
Every one of my weekly reviews has one article that you simply should not miss – and this detailed security analysis of a high security Github exploit is the one. Not necessarily because of this particular vulnerability (although this one was a perfect storm) – but because of the mindset that this puts you in when thinking about the security of your own applications.
Elasticsearch is one of those rare types of software that actually delivers – this article will provide a good and comprehensive introduction to it.
This is a good tool to know – it enables properly tracking the performance of your application and actually knowing when you're introducing a regression. All in all, it's an easy thing to set up and run in your CI.
I know that one of these crops up every couple of months – and I was planning to skip it – but I found that I was taking notes of things to try out – which to me is a sign that it's worth a read if you're working with Git (if you're still working with SVN, I think we should have a little talk).
A balanced, non ritualistic approach to development methodologies – and a reminder that we should focus on being productive and producing good quality work and not obsess or get bogged down in any one process.
Good pointers to get more value out of a code review. Here are another two good articles on the subject:
- => 11 proven practices for more effective, efficient peer code review
- => What I look for in a Code Review
My plan for this review is to give you a good handful of articles to read every week – my own perspective – and filter out some of the noise.
If you have any suggestions on what I should read, to potentially include into the next review, drop me a line in the comments.
Also, if you feel that I missed a gem that came out this week, also let me know – these articles are editable at the end of the day.
Have a great week.