1. Rate today's workshop - scale of 1-10

9 (missing point a reflection on general class structure, not the instructor)

2. Things from today that I liked

Liked the instructor - Beth was able to work with everyone individually as needed while staying ahead of schedule, allowing her to fit in extra material. Liked her focus on helping understand the underlying principles and process and not just relying on the nice extras from fish. Also appreciated checkins to see if anyone was moving faster and slower and the addiditonal challenge

3. Things I would improve request students to read the same unix crash course that is a prereq for F2 - the appendix from ruby the hard way. I did that the day before and found it to be an incredibly helpful primer and even if only half the students read through it it would help keep things moving and allow the class to cover more material.

Perhaps have set up be an optional 30 minute lab before the main course so those who finished set up before can be on same page as those who need help when course starts

OR

have a prepared list of micro challenges to add more structure to those inbetween times when the class is working on a task and you finish ahead of time. Would help having a guide to where to focus energy. Otherwise I would jump down the rabbithole of reading man entries and sometimes getting a bit overwhelmed by too much data

Unix & Git for Everyone (Portland, August 22, 2015)

Pre-work

1. Ensure your laptop up to the task of coding

• Is virus and malware free
• Uses the latest, stable, updated version of its operating system
• Has a functioning screen, keyboard, and trackpad
• Has plenty of free hard drive space and memory
• Can reliably connect to wireless networks

2. Complete the setup guide for your computer's operating system

• Mac OS X
• Ubuntu
• Windows

Following completion of these Pre-work assignments, you should:

• Have a colorized terminal with a Git compatible prompt
• Be able to open files in Sublime Text via the Terminal
• Be able to receive a valid response when typing "git --version"

---

Testing Out of the Workshop

To test out of the workshop, you will need to complete this assignment. Completion of this assignment, whether independently or at the workshop, is due before the start of your Code Fellows course.

Demonstrate the following skills using only your Terminal, your text editor, and your web browser.

1. Create a fork of this repository

2. Clone the fork to your computer

3. Create a new branch called notes

4. Checkout the branch notes

5. Create a directory with the same name as your GitHub username

For example, codefellows

6. Create a unix_notes.txt file in this directory

For example, codefellows/unix_notes.txt

7. Add the notes about what you've learned about Unix to this file

For example,

cd <path> Changes the working directory to <path>
ls <path> Lists the directory content of <path>
...

8. Create a git_notes.txt file in this directory

For example, codefellows/git_notes.txt

9. Add the notes about what you've learned about Git to this file

For example,

git add <file> Adds any changes inside <file> to the staging area
git commit -m '<message>' Commits the staging area to the repository with a <message>
...

10. Add these untracked files to the staging area

11. Commit the changes

12. Push the branch to the origin remote on GitHub

13. Send a pull request from this branch to Code Fellows' master branch