About

I grew up watching my mom run her own painting business in Bozeman. Estimates, scheduling, color theory, client management, all of it. I think that's where I learned that making something beautiful and running something functional aren't actually separate skills. They just look different depending on the day.

I went to the University of Minnesota for fashion design because I genuinely loved it. Pattern making especially. There's something about looking at a flat piece of fabric and knowing exactly how it needs to be cut and folded to become a three-dimensional object that fits a body. That kind of thinking came naturally to me. I was good at sewing, good at construction, and obsessed with how clothes communicate. Why something reads as expensive or cheap before you even touch it. How a silhouette signals a decade. The way trends move through a culture like a slow-moving wave you can almost predict if you're paying attention.

My senior thesis collection focused on world building.

After I graduated I traveled alone through Europe for a while. I ended up in hostels full of founders and developers, people building things I'd never heard of with tools I didn't understand. I came back to Montana and enrolled in a CS degree at Montana State. I wanted to understand what they were doing.

That was the beginning of something I'm still figuring out. Fashion trained me to read a room. Code taught me to read a system. I'm not sure I would have become comfortable with either one without the other.

Outside of work I DJ occasionally around Bozeman, mostly at friends' parties and small venues. My playlists are probably the thing I'm most particular about. I spend an unreasonable amount of time thinking about sequencing, how one song earns the next one, what the emotional arc of a two-hour set should feel like. I go to as many concerts as I can.

I'm also endlessly interested in how trends work. Not just in fashion. In music, in tech, in culture broadly. Every trend has an origin and a logic, and once you start seeing the pattern it's hard to stop looking for it.

I'm drawn to places and teams where design and engineering aren't two separate conversations. Where someone can say "this component is doing too much" and mean it as both a code problem and a design problem at the same time.

I don't think of myself as a specialist. I think of myself as someone who moves between things and brings each one into the next. Fashion into code. Culture into systems. Music into structure.

If something I've made caught your attention, or you just want to talk, you can reach me at sageajames1@gmail.com.