Amir Fahimnia

Method

I work by reduction. Removing what does not carry meaning. Protecting what does. I prefer systems that remain legible over time: clear inputs, explicit limits, few assumptions.

Identity is not metadata. Names are not labels. Interfaces should not misrepresent people. When trade offs are unavoidable, I choose clarity over speed and maintenance over novelty.

Domains

I work on problems around names, attribution, and verification. Mostly where digital systems fail to respect human identity. This includes research, system design, and documentation. It excludes branding, promotion, and visibility work.

Software systems

I design and build software that stays understandable after it ships. Internal tools, constrained public systems, and long lived interfaces. Scale is not a goal. Readability, correctness, and care are.

Teaching

I teach software and design with an emphasis on method: how to think, how to decide, how to explain work clearly. Teaching is not performance. It is shared attention and responsibility.

Working notes

A small set of written materials. Not case studies. Not showcases. Working documents.

1. On verified identity and misuse of artist names
2. Notes on software systems that require trust
3. Teaching structures for critique without spectacle
4. Interface design as responsibility
5. Maintenance as an ethical choice

10110.dev

10110.dev is a separate project. It focuses on protecting artist names, verified identity, and ethical digital presence. It operates under its own terms, rules, and pace.

This site does not explain or promote it. It simply acknowledges its existence.

Visit 10110.dev

Boundaries

I work within clear limits. I do not take on marketing driven projects. I do not participate in growth first or extractive systems. I do not frame work as personal branding.

I work slowly and intentionally. I respond selectively. If something feels unclear or misaligned, I will say so. Silence is sometimes the correct outcome.