English feliratok

← Properties of a VCS for Code - How to Use Git and GitHub

Beágyazókód kérése
5 Languages

Showing Revision 3 created 05/25/2016 by Udacity Robot.

  1. If you were to design a version control system specifically for
  2. code, what would it look like?
  3. In the rest of this lesson,
  4. we'll be discussing many ways version control systems can be different and
  5. what a programmer would want in each case.
  6. Wikipedia and Google Docs are clearly not designed for writing code.
  7. They require you to use their special purpose editors that don't have any
  8. features that programmers tend to want in an editor,
  9. like syntax highlighting and parenthesis matching.
  10. Using Dropbox is a more plausible alternative here since you can use any editor
  11. you want and the files are saved on your computer, as well as in the cloud.
  12. Similarly, when you save copies manually,
  13. you can edit with whatever program you prefer.
  14. Wikipedia also doesn't actually save files on your computer,
  15. which would make it hard to run your code.
  16. Google Drive does let you save your Google Docs files on your own computer, but
  17. they're in a special format that only works with their special purpose editor
  18. and you can't access the history offline.
  19. Dropbox is similar.
  20. Again, you can edit your files on your own computer, but
  21. you can only see the history online.
  22. Manual saving is the only option here that you can use offline.
  23. Of course syntax highlighting and offline access to history aren't the only
  24. areas where programmers would want different features in their version control.
  25. The next feature I want to consider is whether users should manually choose when
  26. to save or whether the systems should save versions automatically.
  27. Let's think about which option would be better for code.
  28. As a programmer, when would you want to have versions of your code saved?
  29. Consider a few different use case scenarios when you're coming up
  30. with your answer.
  31. One option would be at regular intervals, maybe every hour.
  32. Or maybe whenever there's a big enough change, maybe 50 lines or so.
  33. Or maybe when there's a long pause in editing.
  34. Or lastly, when you choose to save a version.