Lots of interesting writeups on Java 9 this week.

Here we go…

1. Spring and Java

>> Spring Tips: Season 2 Recap [spring.io]

A summary of the Spring Tips series, including integrations with jOOQ, Couchbase, MyBatis, and a lot more.

>> Light at the End of the Long Tunnel for Java EE 8 [infoq.com]

Looks like that waiting for Java EE 8 finally comes to an end.

>> Custom collectors in Java 8 [frankel.ch]

Java 8 comes with an overwhelming set of collectors for the Stream API but sometimes even this is not enough and you need to create your own collectors – which might be more complicated than you thought.

>> Java 9 modules – JPMS basics [joda.org]

Another solid guide to modularity in Java 9.

>> Critical Deficiencies in Jigsaw (JSR-376, Java Platform Module System) [developer.jboss.org]

Redhat team raised multiple issues regarding the current implementation of the Jigsaw Project. It looks like there were multiple compromises made when developing the new modular system for Java.

>> 8 Ways to use the features of your database with Hibernate [thoughts-on-java.org]

There are quite a few common misconceptions about Hibernate – one of which is that it can only be used for simple mapping. It turns out you can call database functions, stored procedures, map views, and quite a bit more.

>> Want to Know What’s in a GC Pause? Go Look at the GC Log! [infoq.com]

GC logs can be a source of crucial information if you know how to read it – which can be tricky because GC logging is not thread-safe (prior to Java 9).

Also worth reading:

Webinars and presentations:

Time to upgrade:

2. Technical

>> Stop sweeping your failing tests under the RUG [ontestautomation.com]

Instead of retrying your tests till they green out, it might be a better move to invest into fixing problems with the system, or with the test itself.

Also worth reading:

3. Musings

>> Elements of Helpful Code Documentation [daedtech.com]

Discovering APIs by experimenting with them is fun but not very efficient (especially from the customer side of things). By taking care of documentation, we can get a lot more productive in the long term.

>> Alternatives to Lines of Code [daedtech.com]

It’s not a secret that measuring productivity using LoC/day is less than ideal and can be hacked easily, although it still appears quite attractive to some managers.

Also worth reading:

4. Comics

And my favorite Dilberts of the week:

>> My mother taught herself Ruby on Rails over the weekend [dilbert.com]

>> Does the strategy create itself? [dilbert.com]

>> Setting up my dev environment [dilbert.com]

5. Pick of the Week

>> Unnecessary Qualifiers [m.signalvnoise.com]