- Debugging Philosophy and Techniques
- Basic Errors and Reading an Exception
- Methods and the Stack, Reading a Backtrace
- Error Classes, Throwing and Rescuing
- More Debugging Techniques, a Glimpse of Testing
##Goals 01/07/2014
###git and github
- Understand the purpose of version control systems
- Learn how to manage files/projects with git and github
- Understand git branching
- Understand how to collaborate with others
###ruby part II
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.
For any command we discuss here, the command man, short for manual, will give a (hopefully) detailed explanation of that command. Sometimes that explanation will be too detailed for you. When you get lost in a man page and you want to understand it, start again from the beginning of of the man page and keep repeating. Hopefully you will get further into the page each time you read it.
The command line is my home. I literally think of using the command line as walking around a building.
#WDI Installfest
We are going to install the tools necessarily to program with Ruby and Rails on your computer.
If you are on a Mac which is not running the latest version of OSX, please upgrade through the Mac App Store. Apple has made it easier to set up a computer for software development in OSX Mavericks, and keeping the differences between computers to a minimum will help us get everything installed quickly and correctly.
If you are unsure or run into problems during installation, stop and don't worry; We will finish up any of the loose ends on Installfest. Do not try to troubleshoot on your own, you might break your environment further.
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.
For any command we discuss here, the command man, short for manual, will give a (hopefully) detailed explanation of that command. Sometimes that explanation will be too detailed for you. When you get lost and you want to understand, start again from the beginning of of the man page and repeat.
The command line is my home. I literally think of using the command line as walking around a building.
/ is the entrance - the root directory - but I usually start out in `/Users/rap
