Skip to main content


Showing posts from March, 2015

Deals You Can't Miss

1 Year Subscription

Blocks not Parameters for logging debug information in Ruby

Okay, it really matters if you've got to log your debug information that is more than a plain dumb string without any concatenation. Let's take our typical habit of writing a debug like below: logger . debug ( "This is a " + potentially + " expensive operation") The above snippet could be better written as below: logger . debug { "This is a " + potentially + " expensive operation" } The block form is recommended because the code in the block is evaluated only if the debug log is to be written/logged.  Reference: [Ruby Doc] How to log a message? Book Recommendation: [Book] Ruby Programming: The well-grounded Rubyist

The Bad Developer

"Discipline.. do I look I care?" It takes one rotten apple to spoil the entire cart of A-grade apples. And it takes one, just one #BadDeveloper to spoil the spirit and works of the entire team and hurt the project beyond anybody's imagination - no pun intended here. It thus becomes imperative to quickly identify the behavioural traits of the #BadDeveloper to save the team, project and the business from sinking. Here is a quick list of How-To(s) to find out the #BadDeveloper (or the rotten apple in your development team). How to deal with him is for the other post. How to identify him in your team is the focus of this post. By the way, the list in not comprehensive and I'd appreciate your participation in growing the list by commenting your experience in the comment section of this post. It helps and indeed matters!