NullLogger completely makes sense. NullUser allows code to proceed indefinitely as if we have a User instance and have to proactively check. Doesn't Ruby have optionals?
No, it doesn't but there are some cool gems that provide optionals, like https://github.com/tomstuart/monads#optional. The pattern works pretty efficient, but it often treats just symptoms and the real problems are in the design, like structural coupling or lack of domain concepts.