3 Months of Learning Guitar
I started learning to play guitar about three months ago, so here’s an update on how it’s going and what the experience has been like so far.
What I’ve Learned
I’ve learned a lot so far, but I also feel like I can’t really do much yet. If someone were to watch me play, I don’t think they’d be impressed by what I can presently do. I’m still learning lots of basics.
I’ve been pretty consistent with my lessons and practice. Every Saturday I have a 30-minute in-person lesson, although I’ve missed a few due to travel. This is plenty of time for me to learn something new each time and to have plenty to practice during the following week. I’ve never felt like I didn’t have enough to work on after each lesson.
For the month of June I practiced every day for at least 20 minutes, and since then I’ve been practicing 5-7 days most weeks for 20-30 minutes each time. I don’t think I’ve ever put in more than one hour of practice in a single day. Usually I practice after my workday and before dinner, typically around 6pm. Practicing guitar feels like a nice transition from the workday into the evening.
Here are some things I’ve learned in my first three months:
I know how to tune my guitar in a few different ways. My acoustic-electric guitar has a built-in tuner powered by a 9V battery, so I normally use that. I also know how to tune the guitar using an iOS tuner app. I can play along with a metronome app too.
I can play some simple tunes like “Happy Birthday,” a basic blues sequence, and small parts of a few songs (“Sunshine of Your Love,” “Brown Eyed Girl,” and “Blitzkrieg Bop”). But for the most part, I’ve been learning and practicing basics and not learning how to play a bunch of songs.
One of the first things I learned were the 6 guitar strings: low E, A, D, G, B, and high E. I learned two phrases for remembering them:
- Edgar ate dynamite. Goodbye, Edgar!
- Every acid dealer gets busted eventually
I can play the five chords of the CAGED system: C, A, G, E, and D. And I can play a few other chords as well. However, I can’t always play them consistently without buzzing or muting a string or too.
I’m using a left-handed acoustic guitar, but I had one practice session using a left-handed electric, and it was way easier to play chords on it since the strings are a much lighter gauge. I thought about switching to an electric guitar since I’m sure I could learn faster on it, but I like the acoustic I have, so even though it’s more difficult to learn on it, I’d like to stick with the acoustic for now.
I can read and follow guitar tabs, although I’m slow at this and often have to think about how the information on the tab translates to which fingers go on which frets. The more I practice a tab, the easier it gets of course. I can also read chord diagrams, but again I’m not very fast at mentally mapping them to the fingers and frets; I have to consciously think about how to read them.
I’ve learned upward and downward pick slanting, and I’ve practiced picking in and out of the strings in both directions.
I’ve practiced lots of finger permutations up and down the strings and across the frets. I’ve found this helpful for conditioning my fingers to stretch in the right ways. I’m still practicing these every week.
In the first month, I bought 24 different guitar picks (two 12-packs, one from ChromaCast and one from Dunlop). I tested all of them multiple times to get a feel for which ones I like best. I have a few favorites from each set. I like the 0.73mm and 0.60mm thickness best, although sometimes I go with 0.88mm. I begin each practice session by selecting a pick to use, which is a simple way to get started each time.
Las Vegas is very dry, frequently below 15% humidity, which is bad for wooden guitars. Multiple people at the guitar store recommended getting a guitar humidifier, which is an inexpensive way to prevent damage due to dryness. The store keeps their own acoustic guitars in a separately enclosed, humidity controlled area. If a guitar dries out too much, the neck could bow and other cracks and deformities may occur. So this seemed like a sensible piece of insurance. When I’m not using it, I always keep my guitar in its case with the humidifier, which is really just a small sponge that hangs in a plastic case between the strings. This consistently keeps the guitar at 45-50% humidity, as measured by a small humidity meter that I keep inside the case. Apparently 50-55% would be better, by I’ve been told that around 45% is typically the best we can expect in Vegas unless a significantly more expensive airtight case is used, a case that would cost a lot more than the guitar. I only need to rehydrate the humidifier sponge about twice a month, so it’s pretty low maintenance. So far my guitar is in decent shape. I didn’t know anything about this aspect of having a guitar in Vegas till after I bought one.
Speaking of the case, there were a lot of options to choose from. After doing some research, I opted for a Gator Case, which seemed like a good choice if I ever want to travel with it. The guitar fits nice and snug inside the case. The case has feet too, so I can stand it up vertically if I want. I like the look of my guitar, so I’d have preferred to leave it out in the open or on a stand when I’m not using it, but apparently that’s too risky here, and I’d rather not have it destroyed by dryness, so I always return it to its case when I’m done practicing.
When I first got the guitar, I had a really hard time playing chords on it. I tried over and over and just couldn’t play certain chords cleanly, such as the D chord. I suspected my guitar might need adjusting, so I asked a guitar tech at the store to look at it, and he was able to make some adjustments to the neck that made it a lot easier to play afterwards. The action (distance from strings to frets) on my guitar was pretty high, around 5mm in some places before I had it adjusted. Now the strings are closer to the frets, so I don’t have to press down as hard when I play. At least that early practice with the steel strings toughened up my fingers a lot.
Learning the Notes
Recently I’ve been learning the notes on the guitar, which is complicated. I figured I just had to learn the notes on one string and then I’d know every string. But no! The notes for each string are in different positions, except for the top (low E) and bottom (high E) strings, which are the same.
For example, if I want to play an A note on one of the E strings, it’s the 5th fret. To play an A note on the A string, I play the string open (no frets). On the D string, an A note is the 7th fret. On the G string, it’s the 2nd fret. And on the B string, it’s the 10th fret. So yeah… this was clearly designed by a sadist.
I started with the E strings and learned those first. Initially I practiced all combos of the E, A, D, and G notes. Then I practiced F, B, and C separately till I had those down. And then I practiced these sequences:
- CDEFGABC
- CEGBDFAC
- CFBEADGC
- CGDAEBFC
- CAFDBGEC
- CBAGFEDC
Then I also had to learn the sharps (♯) and flats (♭). And I know that these have multiple labels, like how C♯ is the same fret as D♭.
Eventually I would practice this sequence to cover all the notes for a given string to make sure I had them down:
- C F B♭ E♭ A♭ D♭ F♯ B E A D G
And then I had to relearn all of the above for each of the other strings. That took a while.
I began by learning and practicing one string at a time. The hard part was shifting from single string practice to multi-string practice. My brain had learned the linear positions of each note based on the context of having only one string loaded into my working memory at any given time. Whenever I would switch strings, it took me a few extra seconds to load in my mental map for the new string. But with more practice, my brain is gradually mapping out the full 2D matrix with 6 rows and 12 columns instead of 6 separate 1D lists of 12 notes.
I’m not super fast at this yet, so sometimes it takes me a few seconds to figure out which fret to use, but I thought it best to work on accuracy first, and next I’ll work on getting faster.
To help me practice, I coded up a quick app on my Mac to tell me to play a random note on a random string, selecting from this format:
Play [C,F,B♭,E♭,A♭,D♭,F♯,B,E,A,D,G] on the [high E,A,D,G,B,low E] string
So this generates random notes for me to play like this:
- Play F on the B string
- Play D♭ on the A string
- Play E on the low E string
- Play G on the B string
- Play G on the low E string
- Play B on the B string
- Play F on the low E string
- Play F on the B string
- Play E on the A string
- Play D♭ on the G string
- Play A♭ on the G string
- Play F♯ on the A string
- Play F♯ on the high E string
I can also set the frame rate for how quickly these appear on the screen. As I get used to one speed, I can speed it up the increase the challenge.
For a different mode of practice, I can use text-to-speech and have my laptop read these to me. I can control the rate of speech and set it slower to start, then gradually speed it up as I get faster. This feature is built into MacOS. I coded my app to save hundreds of lines of these instructions to a text file, and if I just add an instruction like [[slnc 2000]] to the end of each line, then the Mac’s speech-to-text feature will add a 2-second (2000 ms) pause. And of course I can change that number to create any length of delay I want. The slnc directive is short for silence; it’s a standard embedded command used by speech to text systems which inserts a period of silence.
See for yourself. If you’re using a Mac, select the lines below, right-click, and select Speech -> Start Speaking. You’ll notice that the voice pauses 2 seconds after each line. There’s probably a way to do this on other operating systems as well, but I’m only familiar with how to do this on a Mac.
- Play F on the B string [[slnc 2000]]
- Play D♭ on the A string [[slnc 2000]]
- Play E on the low E string [[slnc 2000]]
- Play G on the B string [[slnc 2000]]
- Play F♯ on the A string [[slnc 2000]]
If you try the same for the earlier set of lines without the embedded commands, you’ll notice that there aren’t any pauses in the speech, which would make it really hard to keep up unless you’re super fast.
This might seem like a wonky way to practice, but it’s helping me get past this hurdle of learning all the notes and being able to play them faster. I could use the same idea to practice switching between different chords as well. And maybe there are other ways I could customize this little app as well. I’m sure there are much more exciting apps available elsewhere, but I liked the experience of coding this up myself for personal use. It’s links the experience of learning guitar to a well-developed skill I’ve had for decades, computer programming. I see this as a way of telling my brain: You can learn this, and you’re going to get good at this, even it it takes years.
This type of practice reminds me of when I used to practice counting cards at blackjack in my early 20s. First I focused on counting down a deck for accuracy. When I first started, it would take me about a minute, roughly a second per card. Then I practiced for speed. Eventually I could consistently count down a deck in 13-14 seconds, which was as fast as I could flip through and see all of the cards. This gave me a nice advantage in the casinos because my subconscious mind would automatically update the count as soon as I saw a card. I no longer had to keep track of the count consciously. This might sound difficult, but your brain already does this automatic computation when you see certain patterns, like 7 + 5. So it’s just a matter of doing the training, except with guitar there’s the physical aspect of moving fingers around too.
I’d love to reach the point of knowing the notes on the guitar so well that my main limitation is how fast my finger can move to the correct fret and my other hand can play the note. I want the mental computation part to be virtually instantaneous. I don’t need to consciously compute the answer to 3 x 7, so why should I need to consciously compute the correct fret for playing a B♭ on the G string? I want my finger to automatically move to the 3rd fret when I see that.
No one told me to practice the notes in this manner till I have them down flat (oh nice pun!). I just figured that learning the notes really well would be a good step forward and might be useful later on. I think this extra practice allows me to look at the guitar differently as well. Instead of just seeing a bunch of strings and frets, I can see that those strings and frets have another layer of meaning.
Learning guitar can feel a bit distant to me because so much of it is new and unfamiliar. So I keep looking for ways I can link it to something I know. I may not understand flats and sharps too well, but I understand matrices and memorization. I imagine a function whose input parameters are the string and note, and the return value is the fret number, like this
CalculateFret( GuitarString s, GuitarNote n ) -> FRETNUM
So then I’m just teaching my brain to quickly compute the correct return value for all possible input patterns. There are 72 patterns to memorize if I limit myself to the first 12 notes on each string.
I might sometimes learn or practice details that I don’t really need to learn in order to play music, but if this makes the learning experience more engaging and enjoyable for me, I think that’s a good thing. I seem to learn better when I personalize the learning process. I also feel that if I learn this the same way everyone else does, then when will I learn to be creative with it? I think the time to start being creative is while I’m still learning.
What Style to Play?
One of the strangest questions people keep asking me is: So what style of music do you want to play?
That question seems to assume that I have a known destination that already exists, like I want to learn to play jazz or blues or rock. And that isn’t true for me.
My honest answer is that I’d like to learn my own style of play. I want to play Steve-style. I don’t know what that is yet, so I’ll have to explore till I figure it out.
When I first started blogging 15 years ago, imagine if someone had asked me: So what style of blogging do you want to do? My answer would be the same: Steve-style. Today I have a pretty good grasp on what Steve-style blogging looks like, which isn’t a style I understood when I first started. So I figure I can use the same approach to explore and develop my preferred style of guitar music.
Eventually I’d love to compose and play my own songs, but I don’t know what kind of musician I’m becoming yet. How could I know where I’m going style-wise till I get there?
Eventually I’d like to be able to get an idea for a song much like I get new article ideas. Then I want to grab my guitar and just start playing around with it to experiment with how to express the song idea. Then I can refine it, practice it, and play it. If I like it then it would be nice to share it with other people too.
I also think it would be nice to connect with an audience who likes and appreciates what I can create musically, once I’m ready for that. With my current skill level, that audience would be super small right now, mostly comprised of people with serious hearing problems. But that will eventually change as I keep improving, just as it did with coding and writing and speaking.
For me the inspiration to write a new article is very much a form of social energy – I feel a desire to write an article for other people, not just for myself. With this particular blog post, I figured that many people in my usual audience won’t care to read about this topic, but I also sense that a certain subset of people who are interested in learning music as well will appreciate this level of detail and find it interesting. So I’m writing this for those who will appreciate it. I’m already thinking of music in the same way. This may sound a bit strange, but I already feel a timeless connection to the people who will eventually appreciate the music I create and share.
I don’t know what kind of music I’ll create yet, but I do think my writing experience is helping me to approach the creative process in terms of the social flow from the very beginning. Writing and music are beautiful ways for us to connect as human beings. A big part of my motivation for learning music is that I see it as this really rich mode of connection. I would love, love, love to learn how to connect with people through music, not just through code, writing, speech, videos, coaching, conversation, etc.
Process-wise I can envision myself creating songs on the guitar and then arranging more complex electronic versions of them.
For example, here’s the acoustic version of “Personal Jesus”:
So imagine starting with an acoustic version like that and then eventually developing it into this:
I’d love to learn how to start with a simple inspiration for a new song, develop an acoustic version on my guitar, and then if I think it has promise, gradually build it out into something richer on the computer, such as by using Logic Pro.
I’ve written a little bit of electronic music using loops in Garage Band, which you can hear on my Soundcloud page if you want. This was from a 30-day trial of music exploration from 2011. I want to develop my musical knowledge and skills a lot more first before I get back into that aspect, but at least I have some experience with creating basic compositions in software.
I had thought about only sticking with the electronic music side, but since I spend a lot of time on a computer already, I felt drawn to learn a physical instrument. I also enjoy the in-person lessons.
Additionally I’d love to explore how to play music and compose music with other people, once I feel I have enough skill to be able to contribute. I’m not sure how early it would make sense to explore that.
These are my current intentions for where I’d like to go. This may change as I learn more, but for now it seems like I have enough clarity to keep investing in this.
The Experience of Learning Guitar
Overall I’m still enjoying the process of learning guitar. It challenges me in a variety of ways. I don’t feel like I improve that much in a week most of the time, but over the span of the month I can see definite signs of progress. I’m not investing a huge amount of time in this so far, so I think I’m doing okay relative to the time I’m putting in.
There are some aspects of what I’m learning that seem confusing to me still, some minor and some major… oh another pun!
When I look at a guitar tab, the top line on the tab is for the bottom string on the guitar, which feels upside down to me. I have to keep reminding myself that the top is the high E string, but the high E is the physically lowest string when I’m holding the guitar. The low E string is at the top of the guitar.
I don’t get why some notes are just letters and others are sharps and flats. They’re all just frets on the guitar that look pretty much the same. Was this notation invented with an alphabet that only had 7 letters? Why aren’t the notes labeled A B C D E F G H I J K L? Or 1-12? What do we gain from the extra complexity? Someone commented that it’s to keep out the muggles, but I think whoever came up with this was under the influence of a confundus charm.
When I start reading other music terminology, much of it doesn’t make a whole lot of sense to me right now. I can more easily read and understand Spanish, and I don’t know Spanish that well.
I keep looking for elegance in the ways different ideas connect, and I’m not seeing it yet. I’m used to seeing elegance in computer code, and I can recognize elegant patterns in a song, but the system of music terminology and concepts feels like it was invented by Count Rugen, intentionally designed to be overly complex for torture purposes… much like iTunes.
Maybe it’s time for me to study music theory, as some have suggested. Why is it called music theory though? What’s theoretical about it? Does that mean it’s an educated guess at how music works, but we’re not really sure? Does the theory ever get updated with new breakthroughs? Or is it pretty much the same as it was a century ago?
When I learned computer programming, I often visualized coding constructs in physical terms. I pictured code execution as physical movements. Much of the terminology readily lends itself to this. For instance, a loop in coding can be thought of like a physical loop or circle. I would visualize it like running laps around a track. Branching can be thought of like the physical branches of a river or a tree. I usually prefer visual ways to represent certain ideas, which helps me understand them better, but I’m not understanding how certain musical concepts can be visualized this way. I may just need more time to figure that out.
Presently I see a lot of leaves on a tree that look like they’re all from different trees. I’m not seeing the trunk and the branches that give rise to all these different concepts, so I don’t grasp how they all relate to each other. I mostly see a big jumble of ideas that I don’t know how to traverse from one end to the other.
I’d love to reach the point where I have a solid mental map of the realm of music, at least with respect to what connects with guitar. My current mental map is bigger than it was 3 months ago, but it’s still full of holes and gaps, and my brain doesn’t know how different ideas link to each other, so it’s not entirely sure where to put them.
What to Learn Next?
If I could only achieve one type of improvement in the next three months, it would be to refine my mental map of the musical realm that links with playing guitar.
I can see the guitar as a physical instrument, and now I know how to map every fret on every string to a note. That feels like a decent step since it adds a layer of meaning to the physical instrument.
I can also map several chords to finger positions. I can map the knobs at the head of the guitar to their tuning functions. I can map a few tunes to the proper finger sequences.
But my current maps feel like I’m only connecting with small subsets of a much larger tree. I don’t understand what the whole tree looks like yet. It’s like a big blurry blob with some less blurry ornaments hanging from it.
Ultimately I don’t just want to be able to play some songs. I want to understand how to connect the dots between the inspiration to express something musically and what my options are for turning that into actual music that I can play and share. I want to build out a deep, rich, accurate understanding of the whole pipeline of music creation from start to finish. I have those kinds of well-developed mental maps for coding (which allowed me to turn ideas into video games), for writing (which allowed me to turn ideas into articles and a book), and for speaking (which allowed me to turn ideas into workshops and courses). In each case the quality of my results was largely due to the richness of my mental maps.
Good maps are partly built by experience, but they can also be enriched by learning from others’ mental maps, through reflection, through trial and error, and lots of other ways. Mapping the terrain of music is one of the most interesting aspects of this learning process, and it’s also the area where I feel like I could potentially make the most progress in the next few months.
It feels like I still have a long way to go, and that’s okay. It’s good to know that if I just keep doing what I’m doing in this area, I’ll surely know a lot more a year from now. I like that I’m in motion with stable momentum and can expect further progress.