I've been aware of this kind of feature in Rails for some years and I specifically chose to avoid it in this case, as I've never cared for the `find_or_create` type of methods.  It's not entirely obvious, in my opinion, _what_ exactly is getting created, which is what feels magical, and having it spelled out explicitly makes for more readable code.  The argument of less code vs more code feels moot to me, as I try to optimize my code for ease of understanding vs number of lines and a handful one way or the other isn't a big deal.

I see the consistency argument brought up frequently and while I do value consistency, I wonder at what point that becomes obstructive to creative problem solving and starts forcing all solutions down one standard pathway.  For example, if `first_or_create!` didn't exist in the codebase and I wrote this code, then you used `first_or_create!` in some later commit, should I argue against your use of it because I've already solved that type of problem and we need to be consistent?

All of that said, I will change it in the interest of moving this forward.