
From code to product design: connecting UX and technology
An interface can look simple in a prototype and become surprisingly complicated when it has to handle incomplete data, different permissions and situations nobody designed for.
Minha aproximação com design passou pela programação. Sou Richard Barros, empresário, especialista em usabilidade e experiência do cliente e cofundador da Homem Máquina. Antes de concentrar meu trabalho em UX e liderança, já construía para a web.
Part of that journey has been documented on this site since 2007, in posts about CSS, browsers, accessibility and small experiments. Some of those technical solutions have aged considerably. The concern for what happens when someone uses what we build still matters.
What a technical background adds
Having written code changes some of the questions I ask during a project. Where does this information come from? What happens if it is unavailable? Who can change this data? How does someone know that an action has failed?
Those questions shape the experience. A form can look carefully designed and still leave someone wondering whether their registration went through.
They also shape the conversation with engineering. Rather than handing over a visual intention and discovering its limits at the end, I prefer to discuss those conditions while the alternatives are still open.
That does not mean I should decide the technical architecture alone, or that every designer needs to code. It means recognising that a product’s behaviour is built across disciplines.
Following a decision through
Part of a product designer’s work is making a proposal understandable and usable. Another part is investigating whether it addresses the problem that brought the team there.
Imagine an admin dashboard full of information. Before rearranging charts, I would want to understand who uses it and what they need to decide. Perhaps information is missing. Or perhaps an important exception is getting lost among data that requires no action.
The visual solution depends on that distinction. Implementation depends on knowing which information exists, how often it is updated and how it will be maintained.
That meeting point between behaviour, context and making is where I like to work.
Experience still needs to evolve
My technical background gives me a foundation for discussion and investigation. I do not treat tools I used years ago as proof that I have mastered every current technology.
Today, I am also interested in how AI changes products and ways of working. It opens up new possibilities for exploration and prototyping, but questions about clarity, control and responsibility remain.
If a tool suggests an action, can the person check what will happen? Can they correct one part without starting again? Do they understand the limits of the answer?
These questions connect my current interest in AI with longstanding concerns about usability and autonomy. The tool changes; the context needs to be examined again.
Working across disciplines
At Homem Máquina, working with design, engineering and business teams is part of how we build projects. The outcome depends on that collaboration, and the consultancy’s case studies should be understood as team efforts.
My role is most useful where the problem needs to be clarified, alternatives discussed and the product’s intent kept clear throughout delivery.
If you are looking for an experienced product designer or a design leader with a technical background, that combination is worth considering. What matters is not how many disciplines appear on a CV, but how they help someone make decisions.
