[Jon Stratis]

While the small programs we use on these robots may not really require it (back in the day on IFI's old system, pretty much everything we did was in one file!), it is a really, really good industry practice to teach your students. It's called separation of concerns, where you literally separate the different areas. It helps with debugging - if your problem is with your climbing mechanism, you can ignore the files related to shooting or driving, for example. It helps with code understanding - someone new can come in and grasp the general structure and fhedive into details much quicker than they can with a single big file. It helps with collaboration- if you use a repository (like git) to store your code and sync it across multiple people, you have less collisions checking things in, because people are working on different files. This is especially important in the "real world" where you may have a team of 20-50 people working on a single program that's literally hundreds of thousands of line long (or more!), When totaled.