The Room Before the Instrument

On coziness, flow, and the non-functional requirements I forgot to specify

Preface for the Skeptical Reader or What This Essay Is Also Not

The previous essay in this series had a preface like this one. If you read it, you know why it existed. If you didn't, the short version is: synth culture has a talent for turning personal observations into universal prescriptions, and I have no interest in doing that.

This essay is not a minimalism argument. It is not a software conversion story. It is not advice about how to arrange your studio, and it is not a suggestion that your room is wrong.

It is an attempt to name something I hadn't named before — a gap in a framework I published, discovered the hard way, in a doorway, on a Tuesday in March.

If that's useful to you, good. If your room already has flow, you probably don't need this. Read it anyway — you might recognize something.

This essay has a video introduction available.

The Doorway

Every album I finish is followed by a period of silence. Not writer's block — something more refractory. A few months where the studio feels unnecessary, where the urge to make anything simply isn't there. I've learned to trust this kind of biorhythm. Finishing a piece of music - certainly one as large as an album - is a form of exhalation, and we have to take the next breath in before we can exhale again. It's a cycle. It was March when my musical desire swung like a pendulum back towards "shouldn't you be making music?"

The urge returned the way it usually does — quietly, then insistently. A bass riff while doing something else. The particular pull of wanting to sit down and make a new patch. I knew the feeling. I walked to the studio door.

And stopped.

The room was full. Not just occupied — just…dense. Keyboards stacked on keyboards. Stands multiplied until there was no clear path to anything. Cables left unpatched suggesting routing decisions I couldn't quite remember. Every surface held something that needed to be dealt with before I could begin. I stood in the doorway for a moment, felt the familiar weight of it, and went to read a book instead.

This happened more than once.

The "sell it all" thought came, as it always does in these moments. I've learned to recognize it as a false resolution — the fantasy that subtraction will solve what is actually a problem of relationship. I wasn't going to sell it all. I've been down that road twice now in the last decade and it's just a type of reset. But standing in that doorway, I understood that something had to change, and it wasn't the instruments.

It was the room.

The Architecture

I moved roughly two-thirds of the hardware into storage. Not as a statement. Not as discipline. Because the room needed light, and airflow, and negative space. Because I needed to be able to see the ceiling when sitting on my throne.

The result was immediate and, honestly, a little embarrassing in its simplicity. The doorway friction was gone. I walked in and stayed. The room felt like somewhere I wanted to be rather than somewhere I owed a debt.

What changed wasn't the functional capability of the studio. Most of what I moved into storage I could have played that same afternoon. What changed were the conditions under which I could access any of it.

I teach software architecture for a living. One of the foundational distinctions in that work is between functional requirements and non-functional requirements. Functional requirements define what a system does — its capabilities, its features, how it responds to inputs. Non-functional requirements define the quality attributes that determine how well the system can actually deliver on those capabilities under real conditions. Reliability. Maintainability. Performance. Flow.

A system can satisfy every functional requirement and still be miserable to work in. Ignoring non-functional requirements is one of the most common and costly mistakes in software architecture. The consequences don't show up in feature lists. They show up when the system is under load — when you're actually trying to use it.

I had built an entire evaluative framework for synthesizers, named — not coincidentally — the Functional Capability Model, and had not written a single non-functional requirement. The framework could tell me everything about what an instrument does. It had no language for the conditions under which I could actually do anything with it.

The old studio was functionally rich and architecturally broken. I had optimized for capability and starved the system of flow.

The Arrangement

What stayed in the room mattered as much as what left.

The desk: a small computer, a large monitor, a control surface, headphones. No studio monitors at the desk — that's deliberate. Composition happens in my head regardless of physical location. Mechanically these days it's done with a digital sketchpad, on the couch or outside when the weather allows. A sketch started on the couch finishes at the desk without ceremony. The path of least resistance points at writing.

Three flagship hardware synths stayed — wired through monitors, ready to play immediately, deliberately not integrated into the DAW. Recording them requires connecting a laptop. This small friction is also deliberate. The path of joy still points at hardware, at playing sounds for their own sake, at occasionally turning it up and shaking the walls. This is not a compromise between two ways of working. It's a conscious arrangement of the room around my own psychology.

One funky boutique synth stayed. It's a small French synthesizer that functions in this room primarily as an object — angular, unusual, present. It gets played occasionally and noticed constantly. The Functional Capability Model has no category for this. That's the model's problem, not the instrument's.

Coziness

There's an honest accounting to be done about what the hardware is giving me that software isn't, and I may as well make it.

The productivity case for the DAW is real and not close. Project recall alone has saved more sessions than I can count — hardware has a long history of producing some odd magic configuration that simply cannot be reconstructed the following week. Routing is trivial. Resources are effectively unlimited; if a virtual instrument is working, you clone it, which is not a thing that exists in the physical world. Non-destructive workflow means nothing is ever actually gone. The list of conveniences is long and I'm not going to pretend otherwise.

But hardware gives me something a control surface and a virtual instrument don't, and the word for it is power. Turning a filter cutoff knob on a controller mapped to a software synth is functional — I hear the change, I feel the knob. It isn't the same as turning the knob on the instrument itself. Whether this is psychoacoustic, tactile, or simply the effect of a significant physical object being present in a room, I can't fully say. What I can say is that it affects the room even when I'm not playing it. The flagships are there for the moments when I need that particular feeling. Those moments are real and worth designing for.

As I get older I find I'm more sensitive to this. I have a word for it now: coziness. Coziness turns out to be a non-functional requirement for a creative space — not a nice-to-have, but a quality attribute that determines whether flow is possible in the first place.

A cozy room has things in it that aren't waiting for you.

The old studio had nothing that wasn't waiting. Every surface held an instrument with a state, a patch, a routing expectation, a session that hadn't finished. The room was entirely transaction. There was nowhere to rest your attention that didn't incur an obligation.

I've added lamps. Six in total, all low and warm with pull chains for operating them. The Totoro print actually stands out, looking down at me from the wall to my left. The ceiling — the swirled-plaster skinned, ornate, ridiculous, wonderful ceiling. I notice the patterns on it now when I slouch back in my chair and listen. Things that are simply there. They don't change when I don't play. They don't accumulate debt. They hold the room steady while everything else moves. They are flow anchors.

Not Yet

This is not an argument for minimalism, or against hardware, or for any particular configuration of anything. If your room feels right packed to the walls, it's right. I'm not interested in universalizing what worked for me.

What I am willing to say is that the framework I published — and still stand behind — was asking only half the questions. It can tell you what a synthesizer does. It can't tell you whether the room you've put it in will let you access it. Those are different questions, and the second one turns out to matter more than I'd accounted for.

The Functional Capability Model needs a non-functional extension. What are the quality attributes of a creative space that sustain flow? Coziness is one. There are probably others. That's a different essay, and it's not ready yet — I've been in the new configuration for only a few weeks, which is not long enough to speak from anything other than first-week relief.

Ask me again in the autumn.

This essay is a companion to "Synthesizers, Engagement, and the Myth of GAS" and the Manifesto for Critical Thinking in Synthesizer Culture.

Last updated: 2026-04-12