7. Reflecting...

Things we learned about using methods to divide up a story:

1. We can use methods to break up a large amount of code into smaller, manageable pieces (note, this doesn't change the overall amount of code, it just changes how it is organized).
2. If you want your methods to be executed when you hit play, you need to call the methods in the method world.my first method (that's the one we've been working in up to this point).
3. The reason we used methods in this case was for the benefit of the human (aka you), to give the code structure and make it more readable and more manageable. Humans cannot understand and manipulate large amounts of code at one time. By breaking the code into methods, each single method becomes a manageable unit.

Breaking up programs in this way is one use of abstraction to manage complexity in computing. As noted at the start of the module, abstraction is a process of hiding the detail of an operation while still keeping its essential characteristics visible.

Sample questions you should be able to answer after this module:

[Q2.7.1]: What is the best explanation of why we divide code into methods?

[Q2.7.2]: What term do you use to refer to the indicated area below?

Q2.7.2 picture:

[Q2.7.3]: What term do you use to refer to the indicated area below?

Q2.7.3 picture

There are other reasons why it's valuable to use methods, beyond making a program's code body more manageable for humans, and we will go on to explore these in the next two modules.

<< Back Return to: Dividing the Story >>