Unit 7

Lesson 1

1.Why would you want to make your code easier to work with or read? Makes it easier to edit later

Lesson 2

1.Are clean and organized programs more useful for computers or people? Why? They are more useful for people because computers can run anything no matter how complicated it is but people need to be able to follow code so the more organized and clean the more better for people.

2.Try to give examples from programs you've written in class. Using parameters and functions are examples.

Lesson 3

1.What is one reason why parameters and return values are useful ? Reduces the number of code and makes things less complicated

2.What is one way you think programming with parameters and return values may make programming or debugging more challenging ? If you set the parameter's wrong, it will be harder to fix it.

3.What aspects of working with parameters and return values do you feel like clicked today? How to define them and how they work

4.What do you still feel like you have trouble with? I still have a little trouble knowing where to use them

5.How could using parameters and return help you write programs collaboratively? It helps your collaborators be more clear when you are working on it together.

Lesson 5

1.How could you share a function with another person so they could use it in their own program? You could store it in a database that the other person could access

Lesson 6

1.Why do you think it's important to use parameters and return values when writing code for other people to use? It makes easier for them to read

2.What are the benefits of hiding all of the code for filtering the dataset in a library? The benefits of hiding all of the code for filtering the dataset in a library is that it simplifies the code, reduces the chance of bugs (assuming the functions in the library are bug-free), and it makes it more efficient.

3.What information does the user need to know in order to use the library functions? The user does not need to know the inner workings of the functions abstraction, but the user does need to know the documentation so that the user can correctly call the function and understand what is returned (if anything).

4.Why should we test the functions in the library? What does this help us to know?We should test the functions in the library to help us understand and know many things. These include to make sure we understand the parameters, to make sure we understand what the function returns, as well as the fact that testing helps us debug, both the function and the program in which we are using the function.

5.What makes a good library function? How can you make sure that the end users of your library have what they need in order to use your functions? Documentation, local variables, the use of only other functions within the same library, and returns all make a good library function. To ensure end users have what they need to use your library functions, clear and detailed documentation, examples, tutorials, and responsiveness to user feedback and requests are necessary.

6.What are the benefits of using existing algorithms instead of brand new algorithms? The benefits of using existing algorithms instead of brand new algorithms are reduced development time, reduced testing of code, and simplification and identification of errors.

7.Based on what you saw today, add reasons why someone would argue for the following three statements.

• Libraries help programmers collaborate because they allow for sharing and building upon existing code.

• Libraries help programmers reuse code because they provide pre-built, tested, and optimized functionality.

• Libraries help programmers write simpler programs because they abstract away complex functionality.

Lesson 7

1.How does using a library allow you to think about programming at "a higher level"? Using a library allows you to think about programming at "a higher level" because libraries take care of detailed tasks letting us focus on the big picture.

2.How do libraries let you write programs at a "higher level"? Libraries let you write programs at a higher level by abstracting away complex functionality and providing pre-built functionality that can be easily integrated into new projects.

3.Why is testing important when building and sharing libraries? Testing is important when building and sharing libraries because it ensures that the code is functional and reliable, and it also helps to identify and fix bugs and increase confidence in the code's ability to perform as intended.

Test Study Guide