Nathan Day said:
Q1: Caculator!
Q2: One. While one task might have several steps I find that keeping functions small (one task) makes the code easier to read and easier to work with.
This course will become read-only in the near future. Tell us at community.p2pu.org if that is a problem.
Functions allow us to reuse bits of code. For example, say that we are calculating tax on transactions. We can wrap up our code in a functional unit and give it a name:
def calculate_tax(price, tax):
sales_tax = price * tax
total = price + sales_ tax
return total
From then on we can just call that name and pass it some information (called arguments):
calculate_tax(53.79, 0.075)
This will save us time as well as make our code easier to review. Lets take a look at some more in-depth learning resources.
Post chapter excercises and questions below.
Q: What is an example of a machine or process that takes external input and returns a modified output?
Q: How many tasks do you think that an individual function should generally perform?
Q1: Caculator!
Q2: One. While one task might have several steps I find that keeping functions small (one task) makes the code easier to read and easier to work with.
Whoops I didn't make the connection between the slide exercise and this lesson, but here is my code for computepay: