Sure, but as I said, probably not without establishing some culture around it. Just for fun, let's look at shopify's Ruby Style Guide under "General"[0]:

    Avoid mutating arguments.
    Avoid monkeypatching.
    ...
    Avoid needless metaprogramming.
    Prefer public_send over send so as not to circumvent private protected visibility.
    Write ruby -w safe code.
    ...

[0]: https://ruby-style-guide.shopify.dev/#general

Every big company has (and if they don't, they should) style guides. In Ruby people tend to use something like Rubocop (which is a static code analyzer/linter) to agree on a style. That will even be added as a default in Rails 8.