At the very beginning of last year, I decided to track my reading habits and share the best stuff here, on Baeldung. Haven't missed a review since.

Here we go…

1. Spring and Java

>> JUnit 5 – Setup [codefx.org]

A quick intro to what's shaping up to become a very good step forward for JUnit – which bodes well for the entire ecosystem.

>> Reactor 2.5 : A Second Generation Reactive Foundation for the JVM [spring.io]

An update on what's going on with the story reactive systems – seems like a lot of progress is being made.

>> An Ingenious Workaround to Emulate Sum Types in Java [jooq.org]

Some fun pushing the boundaries of java generics.

>> The New Hibernate ORM User Guide [in.relation.to]

A big update to the Hibernate docs, which are now going to 5.1 by default.

>> Memory Leaks: Fallacies and Misconceptions [plumbr.eu]

Some of the basics of what's healthy and what's when looking at the memory consumption of a JVM – simple and to the point.

>> Setting Up Distributed Infinispan Cache with Hibernate and Spring [techblog.bozho.net]

A conversationally written guide on setting up a caching layer for Hibernate with Spring. This will definitely come in handy for at least a few developers out there.

>> The Mute Design Pattern [jooq.org]

Hehe – now let's have some fun.

Also worth reading:

Webinars and presentations:

Time to upgrade:

2. Technical

>> Is Your Computer Stable? [codinghorror.com]

A solid set of tests you can (and should) run against your rig to make sure it's in working order.

>> Stack Overflow: The Architecture – 2016 Edition [nickcraver.com]

Some cool numbers and behind the scene details of running StackOverflow. Very interesting to see what it takes to run SO the old-school way.

Also worth reading:

3. Musings

>> Everything you need to know about the Apple versus FBI case [troyhunt.com]

This is a long read, but an important one given the recent news in the privacy/security world.

>> The Paradox of Autonomy and Recognition [queue.acm.org]

An interesting (yet long) read about office politics and evaluating the work of other developers.

>> High Stakes Programming by Coincidence [daedtech.com]

Committing a fix you don't quite understand is almost never a good idea, and imagining the stakes are high is an interesting way to think about it and quickly reach a decision.

Also worth reading:

4. Comics

And my favorite Dilberts of the week:

>> Why are you picking this vendor? [dilbert.com]

>> Let's just say I'm “comfortable” [dilbert.com]

>> This is tech support. How may I abuse you? [dilbert.com]

5. Pick of the Week

>> Shields Down [randsinrepose.com]


« 上一篇: RESTEasy指南