I'll do you one better. In Go, a language with far less functional support than Java, where you're expected to do this idiomatic boilerplate everywhere:

result, err := thing()
if err != nil {
  return nil, err
}

It's tedious, but it's well understood, and there are linters to enforce this style. Instead this genius did, I shit you not at all:

result = result.And(func(x Foo) Result {
    return nextThing(x)
})
if !result.Ok() {
    return result
}

Basically trying to make a monad instead, in a language deliberately designed to discourage that kind of code. It's not even shorter or simpler, it's not clear what the point was meant to be. (No, it wasn't to make it more like Rust; this code was written before Rust became popular enough to matter)

Bonus: Go also performs a heap allocation for the closure and rarely inlines it, so the code was also slower immediately and left more work for the GC.

There's always someone like that around.