2014-week-review-19
The Baeldung Weekly Review 19
1. Java and Spring
I’m starting this weeks review with a very solid analysis of various types of method invocations in Java, and the performance characteristics of each. This is an in-depth read but very much worthwhile to get a deeper understanding of the Java runtime.
>> Java 8 Friday: Language Design is Subtle
Discussion on some of the Java 8 design decisions such as having default methods versus, for example, Scala traits. A reminder that language design is nuanced and a lot of factors play into it – overall, a great addition to the Java community.
>> Writing Clean Tests – Naming Matters
An in depth discussion about naming in tests – it can serve as a good point of reference for choosing to name your tests artifacts, even if you don’t actually follow all the conventions the article lays out.
>> SpringOne2GX 2013 Replay: spring.io inside and out
This recording is all about Project Sagan and the new (well, new-ish) spring.io website – all very meta and all built in Spring.
>> SpringOne2GX 2013 Replay: Getting Started with Spring Security 3.2
Yes, Spring Security 4 was announced recently, and yes – it looks very interesting. However, if you’re looking to get started with Spring Security, 3.2 is the way to go – this is a quick video that should get the ball rolling.
3. Technical
===== >> ParallelChange
API design is a beautiful thing – here’s an useful process to keep in mind whenever you’re making a backwards incompatible change in an externally published interface.
>> Goto Fail, Heartbleed, and Unit Testing Culture
This article puts forward an important premise – the latest major security issues of 2014 – the GOTO Fail and Heartbleed – could have been easily avoided if the developers were practicing unit testing. Be warned – the article is very long and in-depth – actually going over the tests themselves and showing exactly how the bugs could have been avoided.
>> Is TDD Dead? (the recording)
>> Is TDD dead? [Part II]
The initial “Is TDD Dead” hangout recording and the next one (happening today, on the 16th of May).
The first was OK and spurred a lot of discussion online about the value and practices of TDD, and testing in general, and I’m hoping that the second discussion is going to go a little more in depth.
4. Musings
If you’ve ever seen scientific code, you know how it looks, you know you don’t want to touch it and you know you couldn’t change it reliably if your life depended on it. If you’re interested in that area, of if you were ever frustrated working with a library such as Mahout – this is why.
