100 days of code
Day two of the bootcamp and we’ve already covered a ton of material and I’m trying my best to digest it all. A little overwhelmed, to be honest. I realize now that I’m going to have to drastically adjust my schedule, if I’m going to do well in this bootcamp.
I planned on exercising before class, but I see now that I may have to cut that back to 45 mins-an hour and use the rest of that time to code and review material. In my initial daily schedule, I wrote down that I planned on going to bed by 9pm and I laugh at that now, because I don’t see that happening, at all.
I’ve been taking the teacher’s advice and using the command line, instead of the GUI, for making folders and organizing them. I just created folders and skeleton HTML/CSS files using the command line over and over again and I learned the commands to use for GitHub. This looked really complicated at first, but I think I’m getting the hang of it.
As soon as I’m able to, I’m going to set up my coding practice the way I set up my painting routine. I would never finish a painting in one sitting. I usually start on 7-8 paintings at once and I jump from painting to painting; adding a stroke here and there until they are all finished at the same time. I can see now that GitHub is the perfect tool to do just that; but with code. I’ll set up 7-8 skeleton files and work on different projects little by little until I finish them all.
For those interested, here are the common command line and GitHub commands that I find myself using over and over. It looks complex, but once you know them, you don’t even think about them anymore.
COMMAND LINE COMMANDS:
cd ‘folder’ (change to whatever folder (or directory) you choose)
cd ~ (change directory to home)
ls (list what’s inside the current directory you’re in)
mkdir (make a new directory or folder)
touch ‘filename’ (creates a new file inside your current directory)
git status: check the status of the repo
git add file_name: add one file
git add .: add all files
git commit -m “commit message”: commit your files along with a message. (Do the “-m commit message” to avoid going into the twilight zone. That’s what my teacher said. lol)
git remote add origin ‘https://github.com/username/reponame.git' - the remote url to your GitHub repo
git push origin master - push your files up to GitHub on the master branch (better to use it solo, not on group projects)
git push - push to remote repository
git pull - pull latest from remote repository
git clone - clone repository into a new directory