00:10 <travis-ci> nanoc/nanoc/master aaea09f Denis Defreyne: The build passed.

07:27 <guardian> o/

07:44 <guardian> bobthecow, ddfreyne: are you using "or" and/or "and" when coding in Ruby?

07:44 <guardian> just curious

20:21 <ddfreyne> guardian: No… && and || because their precedence makes more sense

20:21 <ddfreyne> guardian: I even believe Rubocop tells you not to use that

20:24 <guardian> ok

20:24 <guardian> I meant for control flow

20:24 <guardian> like if/unless/rescue

20:26 <ddfreyne> guardian: Yeah, even then. a && b == c && d reads as (a && b) == (c && d), but a and b == c and d reads as (a) and (b == c) and (d)

20:26 <ddfreyne> It’s confusing.

20:31 <guardian> but you're still thinking of boolean operations

20:31 <guardian> foo() or die()

20:31 <guardian> @config[:verbose] and puts "!"