About Joun

The first time I made software was during an office job. Seeing colleagues struggle with an old system, I started exploring alternatives with Excel and Access. I kept asking what they needed, showing them what I had built, and making changes. The resulting program stayed in daily use for about five years, far longer than I had expected.

I didn’t yet know the names for the stages of software development, but I enjoyed listening to someone’s frustrations and turning them into a tool they could use.

I encountered programming again while studying urban planning. I used code to collect and organize data and reduce repetitive work. At first, it was a research tool, but the more I used it, the more curious I became about the tool itself. Eventually, I began studying software development more seriously and started working as a developer.

I began on the backend, working with APIs and data, before moving toward frontend development. I liked seeing results immediately on screen, but I was especially drawn to the place where data and systems meet human behavior. As I worked on different products, I spent more time thinking about what to show and how to make complex features understandable.

Outside work, I make music. I started as a listener and eventually began making it myself, which made me curious about how sound is produced and heard. As I explored creating images and movement with code, my separate interests in music and development began to meet in the same work. These days, I experiment with different tools to connect sound, images, and movement.

These interests were never part of a single plan. A question that comes up in one field often takes me into another, and something I find there makes its way back into earlier work. Sometimes, it is only after making something that I understand what I was curious about.

This site collects what I have made and learned along the way: products I have worked on, personal experiments, and thoughts I am still working through.

Making by Connecting

Writing code often reminds me of writing prose. Just as I divide paragraphs and shape their flow, I divide responsibilities and define relationships in software. Both need a clear sense of what they are trying to communicate and a structure the reader can follow.

I was drawn to similar work when studying cities and building software: observing things that are tangled together, finding relationships, and organizing them into a form I could understand. That is why I value the time spent deciding what the problem is and where to draw boundaries as much as learning new technologies.