PRECOURSE WEEK 2 CONTINUED {Git-ting jiggy with it}

Well. The Git/Github focus has so far felt like a totally different experience from Command Line. I'm currently on lab 24 of Git Immersion, and while I feel like the labs themselves are not that hard, I also feel as though I'm not quite absorbing the information. It's kind of like when a kid first begins learning how to speak --all he or she is doing is essentially echoing words that are broken down into sounds. And while the sounds might come close to being something meaningful, the child has yet to develop an actual sense for what those sounds ultimately mean. I understand the very basics, but beyond that I am still just following directions and doing what I'm told. I have a feeling that after I finish Git Immersion and go onto the Version Control exercises, I will start to have a firmer grasp on Git/Github. Until then, I will concentrate on reviewing each exercise carefully and really thinking about the meaning of what I've done and what I did to achieve it.

Some things I've learned:

- Before creating a repository, first create a directory for your project and change into it, then initiate the repository.

- How to: git add, git commit (with a commit message), git checkout, how to add aliases to git (which are essentially shortcuts so you don't have to type a long command each time)

- How to open a text editor from the terminal (I was using Sublime Text but decided to give it a whirl with Atom)

Things I have to work on:

- How to remove a commit (I learned how to do this, but it isn't very firmly ingrained in my memory)

- using SHA1 hashes (don't entirely even know what this means, except that they are kind of like encoded ID's for your files in git)

- "commiting" everything I've to MY memory, but I think this will happen with time and practice