At the very beginning of 2014 I decided to track my reading habits and share the best stuff here, on Baeldung.

在2014年一开始，我就决定追踪我的阅读习惯，并在这里分享最好的东西，在Baeldung。

2014 has been quite the year, covering each week with a review. I’ve been doing a lot more reading to make sure I cover and curate stuff that has value and is actually worth reading.

2014年是相当不错的一年，每星期都有一篇评论。我一直在做更多的阅读，以确保我覆盖和策划的东西有价值，并真正值得阅读。

Let me know in the comments if you’re finding my reviews interesting and useful.

请在评论中告诉我，如果你觉得我的评论有趣和有用。

Here we go…

我们来了……。

1. Spring and Java

1.Spring和Java

>> How Spring achieves compatibility with Java 6, 7 and 8

Insight into intelligently building Spring with Java 8 support but not actually requiring Java 8.

洞察到智能构建支持Java 8的Spring，但实际上不需要Java 8。

There are takeaways here for anyone who’s maintaining a library/framework/API in Java land.

对于任何在Java领域维护一个库/框架/API的人来说，这里都有一些启示。

>> Spring From the Trenches: Injecting Property Values Into Configuration Beans

If you’re dealing with a lot of properties in your project, this is definitely solid advice to follow – makes managing all of that complexity a lot easier.

如果你在你的项目中处理大量的属性，这绝对是值得遵循的建议–使管理所有这些复杂的东西变得容易得多。

>> Result Set Mapping: The Basics

The first of what looks to be a promising series about working with the JPA and Result Sets.

这是关于使用JPA和结果集的工作的第一个看起来很有前途的系列。

>> How does Hibernate store second-level cache entries

Exploring the Hibernate Cache fun and speed. Lot of things to learn from this piece.

探索Hibernate Cache的乐趣和速度。从这个作品中可以学到很多东西。

**>> Spring Enable* annotation – writing a custom Enable annotation**

An @EnableFoo style annotation can definitely come in handy in complex systems and there’s no reason to be restricted at just the default ones in the framework.

@EnableFoo风格的注解在复杂的系统中肯定能派上用场，没有理由只局限于框架中的默认注解。

>> Log Management Tools Face-Off: Splunk vs. Logstash vs. Sumo Logic

Log Management, visibility, exploration and analysis are oh-so important even for medium-sized projects. There’s just so much you can get out of having a proper log solution implemented in production.

日志管理、可见性、探索和分析是非常重要的，即使对于中等规模的项目也是如此。在生产中实施适当的日志解决方案，你能得到的东西实在是太多了。

These tools also pretty much pay for themselves the first few times you save a good few hours of grepping through your text based log files. The one I regularly use these days is the ELK stack.

这些工具在你节省了几个小时的文本日志文件的搜索时间后，也会为自己带来相当大的回报。我最近经常使用的是ELK栈。

Also worth reading:

也值得一读。

Webinars and presentations:

网络研讨会和演讲。

Time to upgrade:

是时候升级了。

2. Technical

2.技术

>> What Story Does Your Code Tell?

There’s always one more step on the path to writing clean, maintainable code.

在编写干净、可维护的代码的道路上，总是多了一个步骤。

How that code reads for someone who’s not you definitely worth being aware of since so much of the teams time is spent reading code.

对于不是你的人来说，代码如何读绝对值得注意，因为团队的大部分时间都花在阅读代码上。

Also worth reading:

也值得一读。

3. Musings

3.思索

>> Given Enough Money, All Bugs Are Shallow

This is an important lesson for all open source projects and for our industry in general. It’s very pragmatic and it’s definitely a long read, but it has a good chance of nudging the ecosystem along in the right direction.

这是所有开源项目和我们整个行业的一个重要教训。它非常务实，绝对是一本长篇大论，但它很有可能推动生态系统朝着正确的方向发展。

>> Please Direct all Inquiries to My Agent

An interesting idea – no clue if it’s practical or not, but it was fun to read.

一个有趣的想法–不知道它是否实用，但读起来很有趣。

Also worth reading:

也值得一读。

>> Clean Communication
>> BDD by example

4. Comics

4.漫画

And my favorite Dilberts of the week:

还有本周我最喜欢的Dilberts。

5. Pick of the Week

5 本周精选

Earlier this year I introduced the “Pick of the Week” section here in my “Weekly Review”. If you’re already on my email list – you got the pick already – hope you enjoyed it.

今年早些时候，我在 “每周回顾 “中推出了 “每周精选 “栏目。如果你已经在我的电子邮件列表中–你已经得到了精选–希望你喜欢它。