Miss Dada  🏳️‍⚧️

Tonight I did two rants in person (towards @jasonrclark & @olivierlacan) that I otherwise would have done on twitter.

So I guess y'all will have to wait to hear what I think about the .& operator, and whether #rubyconf should be more or less "technical."

I don't understand the .& operator. It seems to be compensating for an ActiveRecord deficiency ('find' methods sometimes return nil).

ActiveRecord find methods return sometimes a single model object, sometimes an array of model objects, and sometimes nil.

Using the .& operator means you can guard against nil. 'current_user && current_user.name' is equivalent to 'current_user.&name'