When the Field Moves 2 - Domain / Specialty / Value

A follow-up to When the Field Moves.

“What do you do?” is usually an invitation to name a field and a skill. I work in robotics. I design interfaces. I build websites for small businesses. These answers are pretty useful. They tell people something about the world we know and what we can do in it. They also give us a familiar way to plan our next move: take our skills into a different field, or stay in our field and learn something new.

I have thought about my own work this way for a long time. Now I want to add a third question. As AI expands the range of things I can make and investigate, what do I want those abilities to make possible? Knowing how to do more things gives me more choices. It also gives me more responsibility for choosing where to spend my attention.

Imagine that producing amazing first prototype becomes much easier. A working program. A readable essay. A website that looks good on a phone. Call these 80-point results: work that meets the enough requirements and provides a useful starting point. There will still be plenty to do between 80 and 100. Yet I think another question will become more important alongside that work. When several good outcomes are within reach, which one is worth pursuing?

Three questions about my work

I find it useful to think about this through three terms: Domain, Specialty, and Value. Together, they describe the world I understand, the abilities I can use, and the direction in which I want to use them. They give me a way to design my next project, decide what to learn, and explain my work to someone else.

Domain is the world in which I work. It includes people, activities, habits, and constraints. Someone who works with small shops needs to understand how orders arrive, how staff divide their time, and what happens when the owner is away. “Commerce” names a field. Knowing what an ordinary Tuesday looks like in a particular shop provides a more useful kind of understanding.

Specialty is how I can contribute. It might be programming, machine learning, visual design, teaching, or experimental research. A specialty gives me ways to notice problems and act on them. AI can extend those abilities, sometimes enough to let me attempt a project that previously required a larger team. The depth I need in each skill depends partly on what I am trying to accomplish.

Value is what makes the work worth doing, to me and to the people it reaches. Saving time is a value. So are earning a living, understanding something, making something beautiful, expressing a personal idea, and feeling part of a community. Some values live in the finished result. Others live in the experience of making it. A person can reasonably care about both.

These three dimensions change one another. Learning a new skill can reveal a possibility I had never considered. Working in a new setting can change what I think matters. Choosing a value to pursue can tell me which skills deserve more attention. I see this as a way to shape my work deliberately, rather than choosing my next move only from the list of jobs my current skills happen to fit.

The same website can serve different lives

Consider a developer who builds websites for small shops. The developer understands online sales and knows how to use web tools and AI. Making a basic site is manageable. Two shop owners arrive with what sounds like the same request: “Please make me a good website.”

The first owner would happily hand over the product details and think about the website as little as possible. She wants to spend her time making what she sells. A service that handles the details and requires very little upkeep would suit her well. The second owner wants to change the photographs, rearrange the pages, and write the descriptions herself. Working on the site is part of how she thinks about her shop. She wants a tool that makes those choices easy.

Both owners want a reliable website. Beyond that shared requirement, they are asking for different things. For one, a good tool removes a task from her day. For the other, a good tool makes an activity more enjoyable and more fully her own. Giving both of them more automation could produce very different reactions.

These preferences can coexist in the same person. Someone may happily automate invoices while spending an hour choosing the photograph for the front page. From the outside, that hour might look inefficient. From the inside, it might be the most satisfying part of the afternoon. We learn more by asking what matters in that particular activity than by assigning the person a permanent label.

My sense is that these differences may become more visible as useful abilities become easier to access. When making something is expensive or technically difficult, much of our effort goes into reaching an acceptable result. As that effort falls, we gain more room to choose how we want to participate. Some people will hand over more of the process. Others will use the help to become more involved. The same technology can support both directions.

This is where the idea of going beyond a perfect score becomes interesting to me. Accuracy, reliability, and finish still deserve careful work. But a common score captures only part of what people care about. One excellent website may quietly take care of itself. Another may invite its owner to keep shaping it. Once a solid result is within reach, excellence can develop in several directions.

Choosing what I want to make possible

The developer has choices too. She might enjoy removing tedious work from people’s days. She might be drawn to tools that help people express themselves. She might care most about making useful software affordable for very small businesses. Each direction could lead to good work. Each would also change what she should build, learn, and pay attention to.

This is where philosophy becomes practical for me. What do I consider a good outcome? Why does that outcome matter? Whose priorities am I assuming? What am I willing to spend time on, even when another direction would be easier to explain or sell? These questions help me decide which opportunities to accept. They also help me recognize when a project is succeeding by someone else’s standards while moving away from what I hoped to do.

I can put the relationship into a simple sentence: “In this setting, I want to use these abilities to help these people experience or achieve this.” For example: “I want to use software to help small shop owners shape their online spaces themselves.” That sentence is specific enough to guide a decision. It suggests attention to editing tools, understandable controls, and useful feedback. A different value would point toward a different set of skills.

The sentence is a starting point. Suppose the developer builds an editor with dozens of options, hoping to give owners freedom. The owners open it, look around, and close it. The choices feel like homework. The developer intended to support expression but has made participation tiring. Watching someone use the tool now provides more useful information than polishing the description of what it was meant to do.

She might try fewer controls, clearer previews, or a way to begin with a nearly finished page. She can use AI to propose alternatives, write code, and question her assumptions. Then she can see what changes. Are owners making choices they care about? Can they get the result they had in mind? Do they return to the tool? The evidence she needs follows the value she is trying to realize.

This gives me a more demanding understanding of “finding my value.” I have to take it far enough into the world that I can learn whether it exists in the form I imagined. An intention gives me a direction. Actual use gives me something to work with. Sometimes I will need better skills. Sometimes I will need a different approach. Sometimes the experience will change what I want to pursue.

It also gives personal branding a concrete purpose. “I am a developer who uses AI” tells someone about my tools. “I help small shop owners shape their online spaces” tells them when they might think of me. The work then has to support that description. A portfolio can show the choices I made, what people could do with the result, and what I changed after seeing them use it. Over time, the projects and the explanation of those projects give people a recognizable picture of my contribution.

Leave enough energy for the next throw

There is a temptation to turn all of this into one large assignment: find the right domain, master the right specialty, identify my true value, and commit. I understand the appeal. A clear direction would save a great deal of wondering. The difficulty is that much of the information needed to choose well arrives through experience. I often have to try the work before I know what it asks of me, where I can contribute, and whether I want to keep doing it.

I think of this as having three darts. The first throw tells me something about the distance and my aim. I can adjust the second, then learn again before the third. But if I treat the first throw as my only chance and spend everything on it, I may have very little left for the next two. The information from that first attempt becomes useful only if I still have the capacity to act on it.

For a real project, that capacity includes time, money, health, attention, and the willingness to be a beginner again. I want to make a serious attempt while keeping its size within what I can sustain. That might mean choosing one kind of user, building one part of a system, or setting aside a limited period to explore a new field. Within that scope, I can work with care. When the attempt ends, I want enough room to decide what comes next.

The three dimensions help me make that decision more precisely. If shop owners barely use my tool, I may have misunderstood their work: a domain problem. If the idea fits but the interface is difficult, I may need to improve my skills or bring in help: a specialty problem. If the tool works well but owners would rather have the task handled for them, I may need to reconsider the value I am offering to that group. Several explanations can fit the same disappointing result. Separating them helps me choose a useful adjustment.

Sometimes the right adjustment is to stay and practice. A worthwhile direction can take time to understand, and an early version can be poor for ordinary reasons. I would like each pivot to carry a reason: something I learned about the setting, the method, the people, or myself. Then changing direction preserves the value of the attempt. The experience becomes part of how I choose the next one.

People have very different amounts of room to experiment. A small trial alongside existing work may be the sensible size of a first throw. For someone else, a longer period of focused study may be possible. The scale can vary. What matters to this strategy is retaining some ability to respond when reality teaches me something new.

Domain, Specialty, and Value can all change. I can bring a familiar skill into a new setting, learn a new method for a problem I care about, or discover that I now care about something different. My description of myself can change with the work. A coherent path can emerge from explaining what I tried, what I learned, and why I chose the next step. I would rather build that kind of coherence than depend on getting the first decision exactly right.

What I hope to carry forward

I expect people to pursue increasingly different versions of a good life as more abilities become available to them. Some will seek greater scale. Some will seek deeper understanding. Some will use automation to spend less time on an activity; others will use it to enter an activity they once found inaccessible. Learning to recognize these values will help us understand other people. Choosing among them will help us shape our own work.

For those who come after me, I would offer these questions more readily than a list of safe careers. What world do you understand? What abilities can you use? What do you want those abilities to make possible? Your answers may change as you gain experience. They can still help you choose a project, build a skill, find collaborators, and explain the contribution you hope to make.

I want to ask those questions of myself too. I want to use the help available to me, pursue work I find worthwhile, and pay attention to what it actually does for people. I want to learn deeply enough to make something good, with enough room left to change my mind. The first throw deserves care. I would also like to be there, curious and ready, when it is time to throw the second.

P.S. New posts arrive a few times a year. Leave your email and each one will land in your inbox, or follow along via RSS.
← Blog

Discussion

Comments require JavaScript and a GitHub account.

Cite as: Alan Synn, “When the Field Moves 2 - Domain / Specialty / Value” (2026), https://alansynn.com/blog/when-the-field-moves-2-domain-specialty-value/. Licensed under CC BY-NC-ND 4.0