Just foodie things :
repeat: {{ Keep code and have food }}

Oof I don't like checking for negatives when there's an Else block anyways. Hanging this up on my wall would trigger me every time I'd see it

If you stomach is null, you have bigger issues than pizza

When you eat pizza:
NullPointerException: you're fucked

Why is it posted on a piece of velvety napkin?

Or, maybe that does make sense.

Someone needs a peer review before merging that to production.

God help the poor user that finds the null stomach branch.

Cringe, wrong tag...

I'm pretty sure that these cringy programmer-speak-merchandise-thingies are either made by non-programmers or just god-aweful ones, the likes you'd immediately fire after their first code-review.

if self.stomach == missing_entirely:
orderPizza()
else:
dont()

Traceback (most recent call last):
<main>, at line 1:
if self.stomach == missing_entirely:
<main>, at line 2:
orderPizza()
orderPizza(), at line 237:
raise RuntimeError("stomach must be present before orderPizza() is called")
RuntimeError: stomach must be present before orderPizza() is called

All of you complaining about the null stomach: Just be glad it isn't functional programming. As then eating would entail creating a clone of you with pizza already in it.

@k0pernikus

@highlight
val me: Person = _
me.stomach
.filter(_==pizza)
.getOrElse(0)
.zipWith
(delivery)
(_.2.order(_.1 * phoneNumber))