Nice, me too!

I kind of wish there was an operator for that, for example if "<>" weren't already in use as an alias for "!=", that would be cool, but of course we can't make that change for backwards compatibility reasons.

I had to install this to get brackets that match in color based on the level of nesting: plugins.jetbrains.com/plugin/10080...

That’s pretty cool, there is plugin called Rainbow Brackets for JetBrains editors that does something similar

100%! I don't know how/why anyone still plays this song.

I only write methods like that by hand if there is some additional logic to add. For example, User.find_by_email could downcase the argument, skip the query if the argument is blank, etc. If it is just a straight DB query, using the generic API signals there is nothing else going on here.

To me, using method_missing to dynamically generate these methods seems like something that adds unnecessary “magic” to Rails and is a somewhat confusing concept to have to explain to new Rails devs. I don’t see how having the attributes in the method name instead of the arguments adds clarity.