08 Feb '14, 8pm

#data #datascience #R #Python (Every line of code is always documented)

Always write commit messages as if you are explaining the change to a colleague sitting next to you who has no idea of what’s going on. Per Thoughtbot’s tips for better commit messages : Answer the following questions: Why is this change necessary? How does it address the issue? What side effects does this change have? Consider including a link [to the discussion.] Avoid unrelated changes in a single commit . You might have spotted a typo or did tiny code refactoring in the same file where you made some other changes, but resist the temptation to record them together with the main change unless they’re directly related. Always be cleaning up your history before pushing . If the commits haven’t been shared yet, it’s safe to rebase the heck out of them . The following could have been permanent history of the Faraday project, but I squashed it down to only 2 commits and edite...

Full article: http://mislav.uniqpath.com/2014/02/hidden-documentation/#...

Tweets

Every line of code is always documented

mislav.uniqpath.com 07 Feb '14, 4pm

Always write commit messages as if you are explaining the change to a colleague sitting next to you who has no idea of wha...

Code Red! Check out these heart-racing styles t...

ninewest.com 10 Feb '14, 8pm

United Arab Emirates Dirham (AED)

metric_fu (4.7.3): Code metrics from Flog, Flay...

rubygems.org 09 Feb '14, 10pm

Code metrics from Flog, Flay, Saikuro, Churn, Reek, Roodi, Code Statistics, and Rails Best Practices. (and optionally RCov)

Clean up your RubyMotion code with Teacup

rubyflow.com 10 Feb '14, 1am

Clean up your RubyMotion code with Teacup Posted by FluffyJack on February 10, 2014 — 0 comments In the past few episodes ...

The lost world Featuring the abandoned Jurong Line of the Green Corridor

The lost world Featuring the abandoned Jurong L...

Interesting, while much evidence of the main railway line that ran from Tanjong Pagar to Woodlands up to the end of June 2...