I think that the best part of writing a blog is to get comments from my readers.
Because I have learned a lot from my readers, I want to “reward” the best comments, help you to learn new things, and (hopefully) encourage people to leave more comments.
The rules are simple:
- I select X best comments that were left on my blog during the previous month.
- I link to these comments and explain why I chose them.
- If the author of the selected comment has a blog, I add a link to her/his blog as well.
Enough with chit chat. The six best comments of December 2015 are (in chronological order):
The Six Best Comments of December 2015
Mihhail Verhovtsov asked me to elaborate the performance of my solution that transforms HTML documents into PDF documents by using wkhtmltopdf command line tool. I selected this comment because it is obvious that my blog post should have provided that information. I fixed my mistake by answering to Mihhail's comment and updating my blog post.
Jagadish wanted to know why my implementation of the SocialUserDetails interface takes a UserDetailsService object as a constructor argument. I selected this comment because it seems that my blog post didn't explain this properly. I hope that my answer shed some light on my design choice.
Tim Stephenson argued that being proactive about performance tuning almost never pays off. This comment deserves be on this list because he definitely has a point. I wish that my answer clarified my opinion about premature optimization. By the way, Tim has a Twitter account. Check it out.
Igal pointed out that if you are installing PostgreSQL 9.5 from the binary distribution, you need to install Visual C++ Redistributable package version 13. This comment deserves to be on this list because it helped me to provide up-to-date information to my readers.
B. K. Oxley reported a problem found from my example application that demonstrates how you can add integration tests into your Gradle build by using the Gradle TestSets plugin. I selected this comment because I really appreciate that my readers report problems found from my blog posts. This is great because it gives me the opportunity to fix them. By the way, B. K. Oxley has an active blog. Check it out.
Stephane wanted to know how he can create a code coverage report with the JaCoCo Maven plugin when he runs his integration tests against an application that is run by using the Jetty Maven plugin. Unfortunately I couldn't help him out (yet), but I wanted to thank him for giving me an idea for a new blog post. That is why this comment deserves to be on this list.