#ruby - 06 August 2019
« Back 1 day Forward 1 day »
[19:58:55] user_corrupt: hi everyone.. I'm going through process of installing ruby gem (jekyll) in order to support local development of github pages site (I guess I need it for bulndling???) latest thing I did was add "export PATH=$HOME/.gem/ruby/2.6.0/bin:$PATH" to .bash-profile, and I am now checking gem paths by doing "gem env".. here are the results:
[22:10:45] baweaver: Going to be giving a keynote at Bay Bridge Ruby Conf in September: https://twitter.com/keystonelemur/status/1158843268135702529
[23:32:33] leftylink: note that `what_team_have_win(c1, c2)` is just a 1-to-1 mapping of `c1 <=> c2` . consider if this may be useful.
[23:36:01] phaul: there is a youtube vid Sandi M doing the gilded rose, which might give you ideas on nested conditions like that
[23:38:16] leftylink: also consider that lines 50-54 are exactly the same as lines 56-60, except for line 50 and 56 are different.
[23:40:27] leftylink: note that the guessed value of the loser's score is not important. this may lead to questions about whether it is appropriate to even ask for a loser's score as a param. perhaps it is wiser to instead simply take the guessed winner and guessed winning score.
[23:41:34] leftylink: .... okay, actually the actual value of the loser's score is also unimportant. so the same idea applies to those as well.
[23:48:21] leftylink: because of me forgetting the polarity of <=>. minus is a good mnemonic for remembering the polarity
[23:48:55] leftylink: and then I must to keep in mind that since team wins looks for the larger, not the smaller
[23:55:39] leftylink: well I was about to write some longer sentences about "some people may dislike `if A; LONG_CODE else return thing end` and prefer `return thing if !A; LONG_CODE` since then one can unindent LONG_CODE