Week 01, Day 01.

What we covered today:

  • Introduction | Orientation | Housekeeping
  • Structure of the Course
  • Introduction to the Command Line

Introduction | Orientation | Housekeeping

Joel's slides

Joel Turnbull - Lead Instructor - [email protected]

Jack Jeffress - Co-instructor / Developer in Residence - [email protected]

Gigi Tsang - Producer - [email protected]

Meggan Turner - Assistant Course Producer - [email protected]

Lucy Barnes - Outcomes Producer - [email protected]

The Office is typically open from 8am to 9pm.

Classroom Culture

  • Hidden jokes in comments
  • Have fun and be positive
  • Support the weakness of others
  • Don’t go too postal at the same time
  • Don’t interrupt each others thoughts
  • Respect each other’s personal space
  • Do phrasing
  • Get comfortable with with being uncomfortable
  • Keep caffeinated
  • Embrace being wrong
  • Be present

Geek | Haker Culture

Share and enjoy.

Books, movies and TV series, stupid memes

The Jargon File

The Tao of Programming

"Kicking a dead whale up a beach"

Links

Newsletters

Meetups

Also, check out these

Other

What will go wrong? Everything. This won't be easy for anyone.

"If debugging is the practice of removing bugs from software... Then programming must be the practive of adding them." – E. W. Dijkstra

The best thing you can learn as a beginner is how to debug.

A Typical Day here at GA...
Time What?
09:00 - 10:00 Warmup Exercise
10:00 - 01:00 Code Along
01:00 - 02:00 Lunch
02:00 - 02:30 Review
02:30 - Beyond Labs / Homework

Breaks for morning and afternoon tea last for twenty-ish minutes and are whenever works best.

In terms of homework, we like to keep you busy until 9 or 10.

We have office hours here in Sydney (except during Week 6 - we have the Spit to Manly.)

Structure of the Course

  • Week 01 - Front End
  • Week 02 - Front End
  • Week 03 - Project 00
  • Week 04 - Ruby
  • Week 05 - Ruby on Rails
  • Week 06 - Project 01
  • Week 07 - Advanced Front End
  • Week 08 - Advanced Front End
  • Week 09 - Project 02
  • Week 10 - Advanced Back End / Advanced Everything
  • Week 11 - Advanced Back End / Advanced Everything
  • Week 12 - Project 03

The Command Line

It's probably worth downloading iTerm 2.

Web programmers have to live on the command line. It gives us fast, reliable, and automatable control over computers. Web servers usually don't have graphical interfaces, so we need to interact with them through command line and programmatic interfaces. Once you become comfortable using the command line, staying on the keyboard will also help you keep an uninterrupted flow of work going without the disruption of shifting to the mouse.

The command-line interface, is often called the CLI, and is a tool, that by typing commands, performs specific tasks. It has the potential to save you lots and lots of time because it can automate things, loop through items etc.

date - Will print the current date and time

which date - Will show the relevant file (will probably return /bin/date)

pwd - Stands for Print Working Directory, will show you where you are in your computer

mkdir - Stands for Make Directory

rmdir - Stands for Remove Directory

clear - Will clear the screen (ctrl + l will do this as well)

reset - Will reset your terminal

cd - Stands for change directory

cat filename - Will show you the contents of the specified file

whoami - Will show the logged in user

ps - Will you show you all running processes

ps aux - Will show you all of the running processes with more details

top - Will show you the Table of Processes

grep - Stands for Global Regular Expression Print - useful for finding files or content

ls- Short for List. This will show you all of the files and folders in the current directory

ls /bin - Will show you all terminal commands

man - Stands for Manual. To use it, follow the man command with another command (i.e. man grep).

Most commands will have additional flags. A flag is a request for more information.

A good example of this is the following:

> ls
Applications Documents Desktop etc.
> ls -l
drwx------   6 jackjeffress  staff   204 16 Mar 15:39 Applications
etc.

#https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/ls.1.html

# cd can do a lot of things!

> cd
# Will take you back to your "home folder"
> cd /
# Will take you back to your "root folder"
> cd FolderName
# Will take you into the specified folder name
> cd FolderName/AnotherFolderName
# Will take you through FolderName and then into AnotherFolderName

# We can make folders in the CLI by using mkdir

> mkdir Projects
# Then we can move into it
> cd Projects
# ls will show most of your files (ones that aren't prefixed by a .)
> ls
# ls -la will show every file (even hidden files)
> ls -la
# This will change to the current directory
> cd .
# This will open the current directory in Finder
> open .
# This will go back to the previous directory
> cd ..
# If you hit tab at this point, it would autocomplete for you
> cd pro
# This will create a markdown file called README
> touch README.md
# To open an application in terminal (can use any application that you have)...
> open -a "Sublime Text"

# This will open the file and show the contents
> cat books
# Will show you the contents, pipe it into the sort program. This doesn't change the original!
> cat books | sort
# The pipe character pipes the output to a command
# This will sort the contents and books, and put the sorted contents into the sorted_books file (it will create the file if necessary)
> cat books | sort > sorted_books
# This will rename the sorted_books to books (and will overwrite the books file if it already exists)
> mv sorted_books books
# This will open and show the contents and books, and shows only lines that have the word script in them (case sensitive!)
> cat books | grep script
# To copy a file, the command is cp (this needs parameters - or arguments. It needs a source and a destination).
# cp source destination
> cp books my_books
# To remove things, use the rm command (this doesn't get moved to your trash! It will delete it permanently and is impossible to undo)
> rm my_books

What happens when we run commands?

# It will go through all of the folders and files that are shown when we run the following command, and use the contents of the files to decide whether it can run that particular program or command
> echo $PATH

Here is a basic bash profile.

Some recommended readings when it comes to the Command Line Interface (CLI):

Homework