Practice
109.studio
109.studio is the name I’m using for my independent practice.
It is where I’m bringing together the parts of my work that have usually lived in different places: software architecture, Drupal and web platform work, technical leadership, applied AI, prototyping, delivery systems, and the slower process of studying how software gets designed and built.
For a long time, I did that work inside companies, agencies, and client teams. 109.studio gives it a clearer shape.
It is not meant to be a large agency or a generic consulting brand. At least for now, it is a principal-led practice. That means the work is built around my direct involvement: helping teams understand the problem in front of them, make better technical decisions, and move from idea to implementation with less confusion.
Where it came from
This page used to describe a framework I called Software Studies.
That framework came out of an older project I worked on between roughly 2006 and 2012. I was trying to make sense of how software connects design, engineering, media, information architecture, user experience, and systems thinking. A lot of the language was academic because I was trying to name things I had felt in practice for years.
The useful part of that work is still here.
I still care about the space between research and development. I still care about artifacts, models, diagrams, vocabulary, prototypes, and the way teams create shared understanding before they build. I still think software is not just code, and not just interface, but a medium for organizing knowledge, behavior, and interaction.
What has changed is the center of gravity.
I do not need this page to present a full framework right now. I need it to explain the practice I am building.
What the practice is for
109.studio is focused on the kinds of technical work where architecture, judgment, and implementation need to stay connected.
That includes:
- shaping early product ideas into something buildable,
- reviewing platforms before a larger investment,
- modernizing Drupal and content-heavy systems,
- applying AI inside real workflows instead of treating it like a novelty,
- improving delivery systems, documentation, and developer experience,
- helping founders and teams make technical decisions they can actually live with.
Some of that work looks like advisory. Some of it looks like architecture. Some of it looks like hands-on engineering. In practice, those things are usually connected.
The pattern I keep seeing is that teams rarely need only “strategy” or only “implementation.” They need someone who can help clarify the shape of the problem, understand the technical constraints, make a plan, and stay close enough to the build to notice when the plan needs to change.
That is the space 109.studio is meant to occupy.
How it connects to this site
I think of damien.house and 109.studio as related, but different.
This site is the personal side. It is where I can write more openly about what I am learning, what I am testing, what I have built, and how my thinking is changing. It can hold rougher notes, older projects, book lists, experiments, and reflections that would feel too personal or too unfinished on a business site.
109.studio is the practice side. It is where the work is framed for people who may need help with a product, platform, technical decision, or applied AI problem. The language there should be clearer, more practical, and easier for a founder, agency partner, or technical leader to act on.
The two sites should support each other.
This site explains how I think – 109.studio explains how that thinking turns into work.
What I am building toward
I am using 109.studio to make a few things more explicit:
- the kinds of problems I am best suited to help with,
- the kinds of engagements that make sense as a solo principal,
- the artifacts and examples that show how I work,
- the difference between experiments, services, case studies, and finished client work,
- the role applied AI can play when it is tied to real systems and reviewed by humans.
Some of this is still taking shape. I am comfortable with that.
A practice is not only a service menu. It is also a way of paying attention. It changes as the work changes. The point is to make the work more visible, more intentional, and more useful to the people who might need it.
Start with 109.studio
If you are trying to understand the professional version of this work, start here:
That site explains the current services, starting points, and areas of focus. This site will continue to hold the longer-running notes behind the practice: the experiments, reflections, reading, and working ideas that help shape what comes next.
Footnote
Earlier versions of this page focused on Software Studies, an older framework for thinking about software as a mix of design, engineering, information, interaction, and knowledge media. I still expect those ideas to show up on this site over time, but this page now serves a simpler purpose: explaining why 109.studio exists and how it connects to the work I have been doing for years.