This video is only a short sample, but you can access the full version and all our other great content by subscribing.Subscribe Now
In this week's video Chris is joined by Derek Prior and they run through the process used to solve a real production bug on Upcase! Check out the PR that fixes the bug discussed in this video for more context.
rails/inforoute summary page to think through the routing.
nmap <leader>bp orequire 'pry'; binding.pry<esc>^
show-sourcemethod provided by pry will print out the source of the specified method, especially useful for library code.
bundle open <gemname>will open the specified gem in your editor.
bundle opencommand so you can run it from within Vim, for instance opening a gem in a new tab with
:Btabedit formtastic, with tab completion of gem names!
bundle show --paths, we can get the paths to each of the gems in our bundle.
ag 'def semantic_errors' $(bundle show --paths), (using
ag, aka the_silver_searcher)
bundle searchsubcommand to the thoughtbot dotfiles in this PR
Remember that when you have a bug on your hands, you are by definition in a place of not fully understanding the system. Feel free to reach out, early and often, to discuss the bug or feature you're working on. Rubber ducking, coined in the Pragmatic Programmer, is a powerful technique!