I picked up guitar seriously about three years ago. Not for the first time — I had noodled around with it in college, learned a few chords, put it down. But this time felt different. I had just started getting into music production, and something about understanding how songs were built made me want to understand the instrument underneath them. So I committed. Daily practice. A teacher. Slow, deliberate repetition of things I could barely do.
What I did not expect was how much it would teach me about learning itself. Guitar has an unusual feedback loop — your fingers know immediately when something is wrong. You hear the buzz of a muted string, the slightly off timing on a chord change, the way a phrase lands when you rush it versus when you let it breathe. There is no hiding from the truth of it. The instrument is honest in a way that most of my work is not.
The DAW as a Mirror
Around the same time I picked up guitar, I started producing music in Ableton. The two practices turned out to be deeply connected — one taught me feel, the other taught me structure. In the DAW, you can see a song the way you see a design file: in layers, in components, in decisions that can be undone. You can zoom into a single note and adjust its velocity. You can hear what a mix sounds like with one element removed. It gives you a kind of analytical distance that playing by feel does not.
A song is just a series of decisions — like a product. The best ones make you forget all of them.
What production taught me is that arrangement is everything. You can have beautiful sounds and a terrible song if the architecture is wrong. The same is true in design. A great color palette and bad information hierarchy still produces a bad interface. Learning to produce made me think differently about structure — what comes first, what earns its place, what needs to be removed entirely.
What Music Teaches About Getting Good at Work
The thing I have carried from music back into my design practice is the idea of deliberate repetition. Musicians do not practice songs — they practice the hard parts. The four-bar section where the transition falls apart. The chord voicing that does not sit right. They isolate the problem and work it until it resolves. I try to do the same now with design: find the part I am avoiding, the decision I am deferring, and go straight at it.
There is also something about musicianship that resists shortcuts in a healthy way. You cannot fake feel. You can fake productivity — you can open a file, move things around, close it, and call it work. But you cannot fake a song. Either it moves someone or it does not. That standard clarifies things. I find myself applying it more often: does this design actually work, or does it just look like work?