Okay so I’m in an advanced programming class centered around design patterns, and our professor was explaining why it’s not always useful to provide a null option for users.
My professor, mind you, is an older man who always seems just a little bit flustered, but still intense enough to keep an entire lecture hall in their seats 5 minutes after class ends (every single time).
So he’s sorta hand waving his way through an explanation of why Dominoes Pizza had originally designed a flawed online ordering system, when some components of his story seemed… Familiar.
He started talking about a person who had been messing around and ordered a weird pizza. Deep in my soul, I just thought, “oh no”.
He mentioned that the pizza had not been covered in either cheese or sauce, because there were null options in the form, and I thought to myself, “it can’t be”.
Then, the final nail in the coffin. My professor mentioned that the user had ordered meat on one half of the pizza, but because it was a badly made pizza with no sauce or cheese, it came scattered all around the box.
To recap. My 70ish year old programming professor, who forbids us from using computers in the classroom, who still teaches with a whiteboard and nothing else, who has taught me more about coding in one lecture than I learned in an entire year of AP CS…
USED NONE PIZZA WITH LEFT BEEF AS A CLASS EXAMPLE