There are better ways to read log files than scrolling hundreds of lines in a terminal window.

Using standard tools in Linux, logging becomes effective and simple. In addition, the tools are versatile and worthwhile to master.

I considered structuring this post based on the tools, but a lot of good resources with that approach already exist. Instead, I have outlined the article based on three scenarios when reading logs: runtime parsing, post-parsing and post-processing of log files.

Commenting code is by some considered a code smell or anti-pattern in itself: code should be self explanatory. I agree that a lot of comments could have been left out in the first place. I think comments serve a purpose though, used in the right way. However, here are three ways not to use comments in code.

Amidst the myriad of books out there, here are five I find worthwhile for all developers. These books do not cover a specific language or technique. Instead they provide a broader spectrum of good advice. If I had to pick one of them, it would definitely be The Pragmatic Programmer – From Journeyman to Master. This book offers some great insights into what the programming profession is really all about, and how to excel as a developer.