In software development there’s a concept referred to as “technical debt.” The debt is created when software code is written in a less-than-optimal way. The computer program works, but has some bugs or inefficiencies that will need to be fixed or improved later. Like other kinds of debt, it can be a useful way to get something done now, but will cost more (time, effort, dollars) in the long run.
The metaphor works well for practicing music, too. Suppose I am working on a passage where a certain alternate fingering would be the most efficient choice. But I don’t use that fingering very often and I’m not completely comfortable with it, so I fall back on a more familiar solution. That gets me playing the passage now with some degree of success, but it also solidifies my attachment to the familiar fingering. Or perhaps my articulation is a little too heavy and thumpy, and I cover that up by adding some slurs in crucial places. That makes the passage work, but means that if I ever want to play it right I’ll have to improve my tongue movement and unlearn the slurs.
In a perfect world I would always tackle the issue head-on: invest whatever is necessary to habituate the alternate fingering or clean up my articulation technique. In reality sometimes a looming performance means plastering over the problem and promising myself I’ll fix it later, at a greater price.
I have found it useful to keep a running list of things I want to improve in my playing, including technical debts that need to be paid off. Incorporating relevant exercises, a few at a time, into my warmups helps me make small daily payments, so that hopefully the next time I need those techniques I own them free and clear.
1 thought on “Music practice and technical debt”
And you just got me to go clean up Glazunov. Thanks Bret.