lesson_1_reflections.txt

How did viewing a diff between two versions of a file help you see the bug that was introduced?
	Nó chỉ ra điểm khác nhau giữa hai phiên bản.
	
How could having easy access to the entire history of a file make you a more efficient programmer in the long term?
	Nhìn thấy sự khác nhau giữa hai phiên bản, giúp chúng ta học được cái gì sai, cái gì đúng. Giúp ta củng cố kiến thức, để từ đó chúng ta sẽ làm tốt hơn. Đó gọi là học.
	Helping me to recall what i wrote, to know what was improved.

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?

	Pros: 
		+ The commit is not too small or too large, so I can decide when to commit.
	Cons:
		+ I have to manual commit it.

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? 

	Because all files in a commit are relate to each other when changing.

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

	git log: to show commit ids
	git diff: to show the difference between two commits.

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

	Because I will know what i changed, and after that I can revert to the previous version right away.

Now that you have your workingspace set up, what do you want to try using Git for?
	
	I'm using Git to commit the work logs, compare between commits to find the difference.