Here we go…
1. Spring and Java
I'm running my yearly Java “State of the Union” survey for 2017. Please take a few seconds to vote.
A very interesting Java 8 memory puzzle, with quite surprising results 🙂
It's not that easy to find a suitable place for common code in Spring MVC apps. This write-up shows a few possible places where you could do this.
Java 9's Project Jigsaw finally makes it possible to define module dependencies to be present at compile time and not at runtime.
This is how you can create and consume a simple REST API using Kotlin and Spring.
Externalizing your configuration allows you to build artifacts once and easily swap configurations during runtime or for different environments. It turns out that Git works great as a configuration holder for such scenarios.
Kotlin is becoming more and more popular and it's important to revisit our Java coding habits and learn the right way of doing stuff in Kotlin.
Also worth reading:
Webinars and presentations:
Time to upgrade:
2. Technical
Shocking no one, having a QA in your team is definitely a good idea.
Also worth reading:
3. Musings
If you don't know how to start a peer group, here is a simple list of steps to follow. You don't need this often, but when you do, it's super handy.
Production is always a source of unexpected problems that can be a great feedback for improving your systems.
Static Analysis and Continuous Testing are two different techniques applied to different areas. Static Analysis will be useful no matter how good your test coverage is, as it will point out potential problems before even running a single test.
Also worth reading:
4. Comics
And my favorite Dilberts of the week:
5. Pick of the Week
I've been following the work on this book for a few months now. It's finally out:
If you're doing any kind of Hibernate work, this is definitely one to get.
res – REST with Spring (eBook) (everywhere)