Skip to content

Instantly share code, notes, and snippets.

Andrew Carmer Carmer

Block or report user

Report or block Carmer

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

A Hacker's Guide to learning rhythm and lead guitar FAST!

I've been playing guitar for over 30 years. I never took formal lessons - only ocassional ones targeted to a specific topic. I love the discovery process and the relationship I've created with the instrument.

Five years ago or so, I had an a-ha moment, which fundamentaly changed the way I approach my learning of the guitar. After internalizing all the content I consumed, I thing I've come up with a formula for learning both rhythm and lead guitar in a very streamlined and systematic fashion. This method will teach you how to find chords across the entire fretboard so you can create chord progresssions for your own songs, or to make it easier to figure out the chords of your favorite songs.

However, what I like the most about it is that it gets you ready to play lead guitar, without putting too much emphasis on the pentatonic scale. Also, it teaches the guitar from the standpoint of understanding its symetry, and dare I say, the mathematics



  • Adds 'ready_for_release' label to the pull request
  • Merges the PR
  • Adds the Merge and Branch to Tracker story
  • Add release_label to Tracker
  • Sets tracker story state to 'Accepted'


  1. Define CRUD.

  2. Why do we use set method_override: true?

  3. Explain the difference between value and name in this line: <input type='text' name='task[title]' value="<%= @task.title %>"/>.

  4. What are params? Where do they come from?

  5. Check out your routes. Why do we need two routes each for creating a new Task and editing an existing Task?


Self Direction Plan - Due Tomorrow


For the final 2 weeks of module 4, we'd like to offer the option to to some extention exploration outside of the cirriculum if you desire.

In class we will be studying the JavaScript library, React.

Past examples of students self-directed study include:


Self Direction Plan

For the final 2 weeks of module 4, we'd like to offer the option to to some extention exploration outside of the cirriculumn in you ddd


Things For Review / Exploration

This is a guide to keep you busy over intermission. What you choose to do here will be highly dependant on what you need to review, ramp up on, or learn.

What should I do??

You don't HAVE to do any of this. You will not be graded, but most likely there are some things here you SHOULD do. I would suggest you do something over break to keep the rust off. At this point you are almost finished with Turing, and you should be a self-sustainable learner. That means you should be able to judge what you need to do. Here is what I would suggest:

  1. Redoing, or doing something much like the mid-mod is good practice for everyone.
Carmer / guidelines-and-expectations.markdown
Last active Nov 28, 2016 — forked from anonymous/guidelines-and-expectations.markdown
Things for Turing students to keep in mind while going through the program.
View guidelines-and-expectations.markdown

Turing Student Guidelines and Expectations

The learning at Turing extends beyond technical training. Equally as important is developing professional skills and creating an environment that encourages learning. As a precursor to a professional career as a Software Developer, we would like to emulate practices followed in a professional work environment. A professional work environment consists of a community of people. In addition to creating software developers, we want to simulate an industry we want to work in. We want to also concentrate on creating thoughtful, engaging developers, to add to the tech industry. Here are a few things that make a good community member at Turing:


If you are unable to attend a day of instruction, let your instructors know as soon as possible. It is your responsibility to stay up-to-date on lessons that you miss. If you need anything or have questions, let your anchor or supporting instructor know. They’ll be happy to help. When on group projects, be sure to l


Group Retro and Feedback


First, take about 30+ minutes and do a retro about your group experience. What's a retro? Think about our friday whole module retro - positives, negatives, and so-sos and actionable things you can improve to better the situation for next time. Here is a short read that may help define retros if you need a little more context. It may be helpful to revisit your DTR conversation too.


"By not giving me feedback, you're preventing me from growing." -Anonymous Student


Route Helper Practice

For the following routes, write out the route helper that will correspond with the verb path combination. For example:

get "/artists" => artists_path

post "/artists" => artists_path

Create route helpers for the following:

You can’t perform that action at this time.