I am a human who likes to make things: tools, music, instruments. I work on the web, on audio, and on knowledge management. Besides that I play children's concerts.
In my main job I work as a principal software engineer. When writing code was the expensive part of this profession, it made sense to have people who only wrote code and handed every other question to someone else. As the cost falls away, we need to ask more holistic questions: Is this good for the person using it? Does it sustain the organisation paying for it? And is it any good for the world it lands in?
Systems theory has been making this argument for decades: you cannot judge a part by examining the part, only by looking at what it is connected to. Whether a product, an agent, or piece of software is any good depends on what you considered as part of the system when you asked — the person using it, the organisation running it, everyone downstream of both. Design ethics asks who is affected, systems theory asks where the system ends. The answers tend to meet. In practice this means I like to be in conversations about the business and the design, not only the implementation — not because I want a complex job, but because that's what the job is.