lesson_3_reflections.txt

When would you want to use a remote repository rather than keeping all your work local?

  When you have collaberators working on your project on GitHub and you don't want them all using your computer.

Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository?

  So you can control what the public sees (MyFarms demo, dev, pre, and prod are perfect examples)

Describe the differences between forks, clones, and branches. When would you use one instead of another?

  (1a) Forking is cloning from one GitHub repository to another on GitHub. 
  (1b) Clones is cloning from one local repositor to another on local or on GitHub. You can also clone from GitHub to local. 
  (1c) Branches are separate parts of one repository.
  (2) I kind of already explained that in the first answer and its parts.

What is the benefit of having a copy of the last known state of the remote stored locally?

   To make merging possible without ruining something.

How would you collaborate without using Git or GitHub? What would be easier, and what would be harder?

   (1) Probably in person, or over Slack or something.
   (2) Collaberation might be faster because you don't have to wait for someone to look at GitHub; you could just go for it!
   (3) You might not be able to go into the specifics in person. 

When would you want to make changes in a separate branch rather than directly in master? What benefits does each approach have?

   (1) When I'm experimenting with something new, and I don't want it to break master (what everyone else sees) before I perfect it
   (2) The benefits of putting something directly on master would be if you need a hotfix; the benefits of using another branch would be the same as #1