lesson_1_reflections.txt~

-How did viewing a diff between two versions of a file help you see the bug that was introduced?

I clearly have saw the spot of mistakes. And it was first time when I use diff in command line. Yooohho!

-How could having easy access to the entire history of a file make you a more efficient programmer in the long term?

Of cource it will be very usefull to see the old code for make decision about evolving project.

-What do you think are the pros and cons of manually choosing when to create a commit, like you do in Git, vs having versions automatically saved, like Google Docs does?

Automatically saving is more mess, because we need more logical decision, manual is the good idea!

-Why do you think some version control systems, like Git, allow saving multiple files in one commit, while others, like Google Docs, treat each file separately?

When file is logicaly bind together the best way is to sync them alltogether.

-How can you use the commands git log and git diff to view the history of files?

Git log command is for view commits. Git diff command used for view diff between two commits.

-How might using version control make you more confident to make changes that could break something?

I can add some features without fear that I will brake something.