Games and modularity
About this video
The video introduces modularity: breaking a big program, like a cozy role-playing game, into smaller sub-problems such as farming, then harvesting. It explains three benefits – easier collaboration, easier testing and debugging, and more readable code – using a car mechanic analogy, and shows that code is organised into modules (files) containing functions (specific tasks).
You'll be able to
- explain what modularity means in programming.
- break a large program idea into categories and smaller actions.
- describe three benefits of modular code.
- tell the difference between a module and a function.
Key words
- modularity
- Breaking a big programming problem into smaller, separate pieces that can be solved one at a time.
- sub-problem
- A smaller part of a big problem that can be solved on its own.
- module
- A file that contains the code for a related set of functionality, like a farming module.
- function
- A named set of instructions that performs one specific task, like harvest.
Transcript
- [Instructor] So you wanna build a game, but how would you even get started? Most games we play have thousands of lines of code. Some even have millions. Try and imagine a program with thousands of lines of code all in a single file. Sounds like a nightmare to navigate and nearly impossible to debug.
So how do programmers do it? We use a strategy that in programming we call Modularity, or in simpler terms, we break down the problem. Say, I wanna build a cozy role playing game. What might that entail? Well, I can kind of break that down into different categories of activities like there's farming, fishing, mining, crafting, and then within each of those categories, I can break it down further into the different actions players might take.
So within farming, you might be able to plant, fertilize, water, harvest, maybe trample. Once I have that breakdown mapped out, I can focus on solving each individual sub problem in isolation, one at a time, instead of trying to juggle all the pieces of the game at once.
For example, maybe I start off by thinking about what it means to harvest, and then I write the code for that small piece of the game. Like maybe the plant returns a random number of vegetables based on how well the player cared for it over its lifetime. Notice how that small sub problem was a lot easier to tackle than the bigger problem.
Build the farming mechanics, and way easier than the big problem of build a role playing game. By breaking down programs into modular components like this, programmers get a lot of benefits. For one, it allows them to easily collaborate with other programmers.
One team can own the farming component, and another team can own the fishing component. And within farming, I can work on harvesting, and my teammate can work on planting. We'll have to integrate the different components eventually, but for now, it's easy for me to focus on my task without having to worry about conflicting with my teammate's code.
Two, it makes the code much easier to test and debug. If I gave you the whole program and asked, "Does this game work?" I bet you'd have a real hard time giving me a definitive answer. But if instead I gave you a real small piece of code and asked, "Hey, does this harvesting code work?"
You could probably verify that without a horrible amount of effort. If we've tested all the smaller components as we built them, we can have a lot more confidence that the final product works. It's kind of like a mechanic working on a car. To check if there's any issues, they don't just take the car out and drive around for hours until something breaks down.
Instead, it's much easier for them to test the individual components. They can check that the brakes work, the transmission works, the HVAC works, and if all the individual components work, then there's a good chance the whole car works too. Three, it makes the code a lot more readable and easy to work with.
Instead of one giant mess of code, we've organized it based on task, which makes it easier to find what we're looking for when we need it. Typically, when we modularize a program, we organize it into different modules where each module or file contains the code for a related set of functionality.
Then within a module, we break down that functionality into individual functions, where each function contains the instructions for performing a specific task. So in our farming module, we might have a function called harvest that contains the lines of code needed to perform the harvest action, and then we might organize the planting related code into a plant function.
Now, we've probably seen modules and functions before when we've used the ones that other people have written, like the random module collects a bunch of functionality related to randomness, and organizes that into functions like Rand and. As we write programs that get bigger and more complex, we need a way to organize our code too, so we're not left with a single main.py file with a giant mess of code.
That means it's time to learn how to write our own functions and our own modules, so we can make our code more reusable, testable, and maintainable. So let's get organized.
Video © Khan Academy, used under CC BY-NC-SA. Watch on Khan Academy. Puzzicle is not affiliated with Khan Academy.