Code already shapes emotions.
Interfaces frustrate, calm, confuse, empower.

I design systems with that in mind:
structure first, aesthetics as consequence.

If your product feels:

• powerful but overwhelming
• flexible but fragile
• elegant but hard to maintain

That’s usually a systems issue, not a visual one.

I work at the intersection of code and emotion.

Not code _or_ emotion.
Not tech _versus_ art.

The interesting work happens where systems shape how people _feel_.

I don’t really design “projects.”

I design orientation:
ways for people to stay emotionally and cognitively grounded inside complex systems.

That’s the thread across everything I do.

The always admirable Moxie Marlinspike released a fully encrypted LLM! I just read about it on @arstechnica.com
It's called: confer.to

I will give it a whirl ASAP. Did you already?

Here to exchange notes, share process, and collaborate.

Interested in design systems, AI in creative work, and making complex things usable.

If that overlaps: hello 👋

My work usually involves:

• systems & workflow design
• UI/UX for web and tools
• information architecture
• visual languages
• AI-assisted creative processes

If your tools feel powerful but confusing, that’s my entry point.

AI didn’t replace my work.
It changed where my attention goes.

Less execution.
More framing, structuring, and deciding what matters.

I’m a systems-oriented designer.

I work between visuals, code, and narrative; designing workflows, interfaces, and structures that make complex tech usable.

Currently building and documenting AI-assisted design systems from Berlin.