Ruby on Rails: Debugging

This is the repository for the LinkedIn Learning course Ruby on Rails: Debugging. The full course is available from LinkedIn Learning.

Fixing bugs is one of the most in-demand (and frustrating) skills for developers. Just when your application seems to be running smoothly—a bug appears. Where did it come from? Is it your code? A bug in the framework? Where do you even start looking for the solution? In this course, David Morales takes a hands-on approach to guide you through techniques and tools you can use to fix bugs with ease. Bugs may be unavoidable, but learning David’s bug detection and troubleshooting techniques can give you confidence and skills that are in demand today for any Ruby on Rails developer.

Instructions

This repository has branches for each of the videos in the course. You can use the branch pop up menu in github to switch to a specific branch and take a look at the course at that stage, or you can add /tree/BRANCH_NAME to the URL to go to the branch you want to access.

Branches

The branches are structured to correspond to the videos in the course. The naming convention is CHAPTER#_MOVIE#. As an example, the branch named 02_03 corresponds to the second chapter and the third video in that chapter. Some branches will have a beginning and an end state. These are marked with the letters b for "beginning" and e for "end". The b branch contains the code as it is at the beginning of the movie. The e branch contains the code as it is at the end of the movie. The main branch holds the final state of the code when in the course.

When switching from one exercise files branch to the next after making changes to the files, you may get a message like this:

error: Your local changes to the following files would be overwritten by checkout:        [files]
Please commit your changes or stash them before you switch branches.
Aborting

To resolve this issue:

Add changes to git using this command: git add .
Commit changes using this command: git commit -m "some message"

Installing

1. Clone this repository into your local machine using the terminal (Mac), CMD (Windows), or a GUI tool like SourceTree.

Instructor

David Morales

Web Developer & Technical Instructor

Check out my other courses on LinkedIn Learning.