Your Principal at APCS High School is pretty mad at you all. There are 100 lockers in Hall C that were open and now some, but not all of them are locked. He does not want to have to send his Assistant Principal out to check 100 lockers. He heard that you are 4 of your friends had what you thought was some fun. All 100 lockers were Open (status O) and now some lockers are locked (status L). You found a master key on the floor and you had cards numbered 1 - 10. You chose a card and then locked the lockers in increments of that number (ex. you randomly chose 5 and then locked every 5th locker). Four of your friends came along and thought that was funny and so they randomly chose a card (you put your card back in the card stack) and then if the locker was open, they locked it but if it was locked then they unlocked it. Please see below: Please print the original array in 10 rows of 10 each. At this point, they should all show as O.

Choose a random number in the range of 1 - 10 and then re-print the new configuration of lockers with O's and L's in a 10X10 format.

Do this 4 more times.

With this list, your principal will forgive you and not call your parent...:)

He would most likely be employed by a gov. agency or homeowner because he has the required skills that have to be known to apply and get hired into those jobs.

I'll be your friend lol.

True.

The main part about version control is that you have a repository, which hosts files. any changes done to those files are recorded and, as such, can be reverted back. it is kind of like google drive/google docs (except not as "real-time autosave"). usually these files involve code. version control can usually record changes to files and the lines of code themselves.version control is used by developers, mainly with coding. this may include websites, software, video games, etc. it is very useful in terms of practicality and collaboration.  reverting back a previous version of a file is very useful in the coding/programming world. suppose a programmer adds in something new to a file, a code snippet or two. then he changes his mind because he does not like the feature he coded in (it does not work, inefficient, with version control, he can easily revert back the changes he made.  version control also makes it easier to collaborate. oftentimes, you can use an online, remote  repository such as github or bitbucket. a team of people  can each  connect their computers  to this repository and be synchronised with the source code.recording your changes is also for teamwork  as it tells you who did what. changes can be monitored as well.  online repositories (like  github) may also contain  features to talk about issues with the code, and you can  reference them in the changes.version control also allows you to have different versions of the same thing. there are open source projects where anyone able can contribute to the project; such collaborators are able to create a new version (a new "branch") from the master branch. in this new branch derived from the main master branch, one adds their code and such.  in time, the original developer will look at this branch; they can add all or some of those changes to the main branch if they approve.