A function is like a coffee machine
– 1 –
It needs inputs to work (arguments):
— ground coffee beans (or pods if so inclined)
You can choose to put different blends of coffee into your machine (choice of what argument to pass to function)
— 2 —
You press the "On" button—this is equivalent to calling the function.
You can almost see the similarity between the typical "On" button and the parentheses ( ) used to call a function in Python!
— 3 —
When you call the function/press the "On" button on the coffee machine, the machine will "do stuff" inside.
If you just care about drinking your coffee, you don't care what's happening inside the machine…
If you're an engineer building your own coffee machine, or you want to open up your coffee machine to fix it or—ahem—make improvements, then you _do_ care about what's happening inside the coffee machine.
— 4 —
When the coffee machine does its thing, hot, liquid coffee will emerge from the machine.
You could say the coffee machine _returns_ liquid coffee.
but, there's one problem…
The coffee flows directly into the drainage tray at the bottom of the machine and will likely overflow, making a mess on your kitchen bench…
You called the function like this:
and therefore, the coffee returned is not collected and stored in anything…
Instead, you should put a coffee cup in the machine when you turn it on:
>>> cup = make_coffee(
Now, you no longer make a mess on the kitchen bench you’re collecting what’s returned into something
There’s a fuller version of this analogy here, too:
Addendum (some sad news): Since taking those pictures for the article, that sole remaining espresso cup has suffered this fate
I was told I can’t say Rest In Pieces
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.