Monday, May 6, 2013

Gradual clarity

The weekend is over, boyfriend is gone for 2 weeks, and I now have ample time to learn about GitHub!

Thankfully, my day at work is shaping up to be slow, so I've copied some pages of the GitHub crash-course into a word document to covertly study up.

Here are some important things I've learned about today:

  • staging and committing
    • When you stage a file to be committed, at the moment you give the command, the file at that instant is what will be committed. If the file is modified after it is staged but before it is committed, you must "git status" and "git add <file>" AGAIN to update what will commit.
    • The "add" command is pretty versatile.
  • Branches
    • I understand what a branch is now. Mr. Ryan tried to explain them to me but I think he gave me a more advanced definition than what was necessary. Now I get it.
    • Branches are complicated when working in small groups because merging with the master branch may/probably will cause conflicts. Boo!
GitHub is shaping up to be a pretty cool tool.. I added a crap-ton of files to my repo yesterday, but mainly they consist of answers to python questions on CodingBat, Project Euler, and other misc projects. Nothing fancy. Most of it is bullshit, like a tiny text-based game I made for my friend Dean about thugs who steal swag, or a simple tip calculator that I also made for Dean, while we learned Python basics together.. 

..but anyway, I figured adding these to my n00bc0d3r repo would help me understand what GitHub has to offer. After I think I have a decent foundation concerning GitHub I'll start diving into the Flatiron Prework, experimenting on my own, and looking to projects that I can work on with others.

For now please enjoy perusing through my n00bc0d3 above or take a gander at this accurate artist's depiction of my computer:

No comments:

Post a Comment