mod_0_session_2_readings.md

Session 2 Readings and Responses

The readings and responses listed here should take you approximately 65 minutes total.

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Learning Fluency by Turing alum Sara Simon (35 min)

• Your key take-aways OR how you're going to implement specific points (minimum 3):
• Creativity is a key that can open many doors and also help us to change our perpestive. It really does not matter if our back ground is not even close to technology, but thanks to effort and be creative we can take the best experience use it as a tools for this new change, even when they don't really looks related with each other, we can dig and find it. -In order to become good and be familiar with a new skill or language, patience and persistence are crucial. The memorizing technique that she explained to learn mandarin is really interesting, because I understood that constant little steps and disipline, are the best way to achieve greatness.
• Fluency before understanding is a great message that I kept from this article. I still have to think more about this but so far the message that I got was the power of consistency.

Git Commit Messages (17 min)

Read this article on git commit messages

• Your key take-aways OR how you're going to implement specific points (minimum 2):

• A diff will tell you what changed, but only the commit message can properly tell you why I believe this one of the most important phrases for this article, because with this in mind I found the properly way to use each command depending the context 8
• Tip 1, 2 and 6: For these Tips is important to undestand what type of commit do you need: "Subject" or "Subject + Body and some characters advices for each one. The first concept (Subject) is usefull when you made a simple change and the reader can easily understand it, for this concept is recommend use git commit -m () and not longer than 50 characters. The other concpet (Subject + Body) is useful when you made a change and require a detail explanationof it, in this case the body is where the message must be added and is recommended be not longer than *72 characters *.
• Tip 3 and 4: These Tips are related to some grammar advices for our subject line: Capitalize the subject line and Do not end the subject line with a period
• Tip 5: Writting our subject lines in Imperative Mood help our message to be more efficient, helps readability and avoid confusions.
• Tip 7: Use the body to explain "How & Why". We must be precise and clear in our changes, always having in mind this two questions.

What's the use of the staging area in git? on Stackoverflow (15 min)

The idea of the staging area is frequently one of the trickiest concepts to wrap your head around when you're first learning git. Read the question and answers (or do your own Googling on the git staging area). Then, create your own metaphor comparing the staging area to something in real life.

• Type your metaphor below:

I like to see the staging area as a external cloud memory but inside of my computer. Is a safe place where I can save and prepare my file before to move on, also I like to think about it as a Agent that will help me to conect and organized my files with others.

Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would like an instructor to address, list them below: