7 ms·
I don't find this to very useful, and I think the approach of this study is probably not so great. My background on this is that I'm a professional violinist. I
by ianamartin 12y ago
I don't find this to very useful, and I think the approach of this study is probably not so great. My background on this is that I'm a professional violinist. I started playing when I was 4 and was performing professionally when I was 8. I'm 35 now, and I still play as a soloist, in chamber music, and with an orchestra. I happen to make most of my money by writing code, but the violin is still a big part of my life. I teach kids, and they win big important violin competitions.
My specific issue with this article is that it seems to think of practicing as one monolithic event--as though you are really just doing one big thing when you practice: getting better at what you are practicing. I think the concept of randomizing tasks is sort of getting at a good point, but it's really not all the way there. And also, you have to understand that you are, in fact, getting something extremely valuable out of the block practicing: the ability to focus on a singular task for a long period of time. That's a skill itself. You will never do well in a 3-5 hour rehearsal with a string quartet or an orchestra if this is not something you are accustomed to doing on a regular basis.
Here are some more details.
The big thing to do when I was a kid was to send your children to a practice camp like Meadowmount, where all the Juilliard School teachers spent their summers teaching kids like me. That was all block practice. 5-8 hours a day, and a lesson every day or so. That kind of block practicing went exactly as described in the article. An hour of scales, and hour of etudes, an hour on a piece of music, etc.
In my opinion, that's a mixed bag. You need to be able to pull a scale out and just lay it down. Any scale. Any time. It's a kind of a musical Fizz-Buzz problem. You just need to be able to do it even if it's not really interesting. Although, it's not like Fizz Buzz because scales are actually really hard. Etudes are a sort of micro-problem to solve. You isolate a particular bow or finger technique, and you spend some time every day working out that physical skill--the logistics of getting x fingers from point a to point b in the requisite amount of time.
Putting in a block of time on your musical piece is also important in itself because you have to commit that music to memory. Not just the notes and the finger motions involved, but all the little things like the bowings and phrasings and dynamics and stuff. The parts that take notes and turn them into "music."
The reason I think the study is flawed is that I think it's studying a strawman of an idea. No great players actually practice in the way that this article describes. There's this idea of a mindless slaving away that we do for hour after endless hour. That's not real. I mean, it's probably real for some people. But great players don't do that to begin with. And good teachers don't recommend this approach.
There are some popular methods of learning difficult things. There's a thing that people do to tackle a difficult bit of notes where you just practice slowly with a metronome and you gradually increase the tempo. Start with a tempo slow enough for you to get the notes out, no matter how slow. Then you just gradually make it faster and faster. This should work, right? No. It should not work. And it doesn't work.
--a brief interlude before I explain why that doesn't work--
What you're doing when you play a musical instrument is that you're solving physical problems--usually without the necessary tools. You are working a variety of physical challnges. The logistics of moving fingers from one place to another, you're solving acoustical problems by managing the friction between your bow and your string(s). Or if you're a wind player, you're dealing with the physical properties of your breath interacting with a vibrating reed or you're vibrating your lips when you play a horn of some kind. There are two parts of every musical problem. 1. There's the conceptual problem: "How should I be trying to execute this solution?" 2. The physical part: "How do I train my fingers, arms, hands, lips, whatever to perform this solution?"
Tempo matters when you are planning out these solutions. A slow tempo uses different physical motions, and it takes a different mindset. Slow tempos (yes, tempi, I know, but I don't feel like the word is so foreign that I need to pluralize it in Italian, so tempos) allow for larger motions and gestures. Slow tempos do not need to have efficient motions the way fast ones do.
--back to my point--
Practicing slowly will never get you to perform things quickly. You are practicing the wrong thing. If you want to learn to play things quickly, you have to practice them quickly. But in small chunk. Take 2 or 3 or 5 notes. Play them even faster than you ever intend to perform them, and do it with a metronome, so your rhythm is good. Chain them together, and gradually slow down and enlarge your motions.
I don't know the details of this study: who were the participants, where they came from, or what their experience is. But to me, this seems like a situation where the block practicers are basically dumb practicers. Because no good musicians practice that way. I think you would have positive results doing absolutely anything to break up this kind of a thoughtless, put-in-some-time-and-hope-I-get-better kind of a routine. Random exercises are probably better than that.
I can see how these results make sense. Randomization is probably a good thing for a certain type of musician. But I would argue that it's definitely not better than a thoughtful, focused, problem-solving approach applied for long periods of time.
Anyway, just thought I would throw some things out there. Cheers.
- Stratoscope 12y ago> Tempo matters when you are planning out these solutions. A slow tempo uses different physical motions, and it takes a different mindset. I can totally relate to this. I play harmonica, and what I've been working on for fun lately is the vocal parts from some Fleetwood Mac songs: Dreams, You Make Loving Fun, Gold Dust Woman, etc. My goal is that when I play these songs, it almost sounds like Christine or Stevie singing. (Yeah, you may say, dream on! Humor me...) Now these are not complicated vocal parts, but given my lack of musical talent, I definitely had to slow them down to learn the notes. You might think that the vocal part for Gold Dust Woman is pretty simple, and you'd be right. But it took me quite a while playing it slowly just to learn the notes. And that was the easy part! I could play the notes, but they sure didn't sound like anything you'd want to listen to. I still had to practice and practice the breathing and intonation and whatever you call it that makes the instrument sing instead of just playing a bunch of notes. I'm getting there, but man is it a lot of work. And this isn't something that can be slowed down. Can you imagine You Make Loving Fun at a slow tempo? What would that even sound like? So it's full speed ahead with these songs, and thank you Christine, because You Make Music Fun.
- yonibot 12y agoWould love to hear more about your background - At what point in your life did you get into coding? What sort of coding work do you do?
- ianamartin 12y agoI started doing database work in my mid-late 20s. 27. I had a certain girlfriend who didn't care for my itinerant lifestyle and the ups and downs of being a performer. She wanted me to get a "real" job. I've always been fond of technology, but never a hacker. I messed with a lot of hardware when I was a kid; worked for the hardware repair shop at university when I was in school. Did a lot of troubleshooting, but never any code. I read a couple of books about databases, built some toy applications, and completely lucked into a job with a market research company. They were desperate for someone who could query their db on the fly and work with MR people to do ad hoc reporting. So I did that. Later, I got more into the research aspect of the data I was working with, and moved to the analytics team. It was a good match. Went back to school for statistics, stayed in the market research industry for a while but I got tired of grinding through stuff in databases all the time. I learned some Python for a couple of things, and now I'm at a payments processing company (not one of the big ones that sometimes get talked about here). Still fairly heavy on the DB end of things, but doing a lot of Python and C#. Python for AI on our transaction data--and anything else I can get away with using it for, C# for building reports of various different kinds. SQL Server for all the DBA needs. I'm not looking to move jobs (this one is really too good to quit at this point in my career), but I am looking for part time python web dev work so I can get some experience there. That's where I want to be in 5 years, but I don't want to have to start over as a junior developer to get there. I've got plenty of free time, and I'd love to do 20-30 hours a week for a shop that could offer some mentoring to someone like me. And some cash. But the mentoring is more important. Thanks for asking, by the way. I appreciate it.