Most people told me to pick one. Here is why I never did and what carrying both has taught me about creativity, discipline, and what music is actually for.

At some point in my life, on more than one occasion, someone told me I needed to pick one.

Engineering or music. The practical path or the creative one. The career with a clear trajectory and a defined market or the one with no guarantees and a famously unfavorable economics. The version of my life that made sense on paper or the one that made sense to me.

I never picked one. I am still not picking one. And I want to tell you why, not as a motivational argument for following your passion, but as an honest account of what carrying both actually looks like and what it has taught me about both.

THE ASSUMPTION UNDERNEATH THE ADVICE

When people tell you to pick one they are usually operating from a reasonable assumption that they have not examined carefully enough.

The assumption is that creative work and technical work compete for the same internal resource. That the same capacity for focus and depth and energy that goes into engineering cannot simultaneously go into music. That you cannot do both at a high level because doing either at a high level requires everything you have.

There is truth in that assumption. There are real constraints. Time is finite. Attention is finite. The version of music I would make if I had no other professional demands on my time would be different in some ways from the version I make while also maintaining an engineering career. I am not going to pretend otherwise.

What the assumption misses is that the two disciplines do not draw from identical wells. They draw from different places in the same person and they replenish each other in ways that make the total output of both larger than it would be if I had committed to only one.

Let me be specific about how.

WHAT ENGINEERING GIVES MUSIC

The most obvious thing engineering gives my music is the technical knowledge I have written about elsewhere on this blog. Understanding signal flow, acoustic physics, electrical noise, harmonic distortion, and the behavior of audio equipment at a component level gives me an advantage in my home studio and in my understanding of what gear actually does versus what marketing says it does.

But that is the surface version of the contribution.

The deeper version is that engineering trained me to think in systems. To ask not just what is happening but why it is happening and what would have to be true for a different outcome to be possible. That kind of thinking applied to songwriting means I approach a song the way I approach a design problem. What is the system trying to do? What is the signal I am trying to transmit? Where is the noise entering? What is the most direct path between the input, which is the emotion or the experience I am working from, and the output, which is what the listener feels when they hear it?

Engineering also gave me a relationship with failure that music alone might not have. In engineering you build something, it does not work, you find out why, you fix it, you test again. The iteration is built into the process and the failure is information rather than verdict. I brought that framework into songwriting and it changed how I relate to a song that is not working. Instead of taking it personally I ask what is wrong with the system. Then I fix the system.

WHAT MUSIC GIVES ENGINEERING

This direction of the exchange is less discussed and I think more important.

Engineering is a discipline that rewards precision, repeatability, and the elimination of ambiguity. Those are genuine virtues in a technical context. They are also, if they become your only mode of engaging with problems, a significant limitation.

The most interesting engineering problems are the ones that do not have a clean analytical solution. Where the constraints are ambiguous, where the requirements are not fully specified, where what you are building is not yet well defined enough to optimize. Those problems require a different kind of thinking, one that can tolerate uncertainty, generate possibilities without immediately evaluating them, and hold multiple incompatible framings simultaneously until one of them reveals itself as most productive.

Music trained that capacity in me. Writing a song requires you to work in a space where the destination is not known in advance. You are not solving for a specified output. You are discovering what the output should be through the process of trying to create it. That is a fundamentally different cognitive mode from engineering problem-solving and it is one that transfers directly to the ambiguous, open-ended engineering challenges that the purely analytical approach struggles with.

I am a better engineer because I make music. I believe that without qualification. The creative flexibility, the tolerance for ambiguity, the willingness to try something that might not work and learn from it, all of that came from and is maintained by the music.

THE PRACTICAL REALITY OF CARRYING BOTH

I want to be honest about what this actually looks like in practice because the theoretical case for doing both is easier to make than the daily reality is to live.

Time is the primary constraint and there is no version of this that does not require making specific choices about how time is allocated. I protect music time the way other people protect workout time or family time. It is not what happens with the leftover hours after everything else is done. It is scheduled, defended, and treated as a professional commitment rather than a hobby that gets attention when circumstances allow.

This means saying no to things. Social commitments that feel optional. The extra project at work that is interesting but not essential. The version of my evenings that would be spent passively consuming rather than actively creating. None of those choices are comfortable all the time. They are consistently necessary.

It also means being honest with yourself about the difference between rest and avoidance. Rest is necessary. Both disciplines require it and the creative work in particular benefits from periods of deliberate disengagement. Avoidance is when the rest becomes a reason not to do the work that is actually possible to do. The line between them requires regular examination.

The scheduling reality in my life looks like this. Engineering work happens in the hours that belong to it. Music work, recording, writing, practicing, performing, working on the blog, managing the business side of the Tony Oso brand, happens in the hours I have specifically protected for it. Neither bleeds into the other's time if I can prevent it because the cognitive mode required by each is different enough that the bleed is inefficient for both.

There are weeks where this holds cleanly and weeks where it does not. The goal is not perfection. The goal is a consistent enough structure that both disciplines get real attention over time rather than one consistently cannibalizing the other.

THE IDENTITY QUESTION

There is a version of this conversation that is really about identity. About what you call yourself when someone asks what you do. About whether being both things makes you neither thing fully.

I have stopped finding that question interesting.

What I am is what I do. I do engineering and I do music and I have done both long enough and seriously enough that neither is a hobby or an aspiration. Both are real. Both produce work that exists in the world and that I am accountable for. The label question is a distraction from the work question, which is whether both are being done at the level they deserve.

I think the pressure to identify as one thing or the other comes partly from how professional identity works in our culture, the résumé logic that says you are most legible when you are most specialized, and partly from the discomfort other people feel when someone does not fit a familiar category. The engineer-musician is not a common archetype. It makes some people uncertain about how to relate to you. That uncertainty is their problem to manage, not yours.

What you are is the sum of what you do seriously over time. Do both seriously. Over time.

WHY I WOULD NOT CHANGE IT

The music I make is shaped by everything the engineering career gave me. The technical precision, the systems thinking, the failure tolerance, the understanding of physical acoustics. Those things are in the recordings and in the way I approach a live show and in the way I think about the business of being an independent artist.

The engineering work I do is shaped by everything the music gave me. The creative flexibility, the ambiguity tolerance, the ability to work toward an undefined destination and trust the process of getting there.

Each discipline is better because the other exists. That is not a trade-off. It is a compounding return on a decision that most people would have resolved by picking one.

I did not pick one. The music is better for it. The engineering is better for it. And the version of myself that carries both is more complete than either half would be on its own.

That is the only argument I need.

Tony Oso

Stream Tony Oso at tonyosomusic.com/music

Subscribe at tonyosomusic.com to stay connected. If you are trying to figure out how to carry more than one serious thing at a time, I will keep writing about what that actually looks like.