Why Are Designers Afraid of the Codebase

As designers, we are encouraged to learn visual design, research, psychology, accessibility, and business thinking. But we rarely talk about understanding the systems we design for.

Through my experience contributing to an open-source healthcare platform, I discovered that understanding a codebase is a design superpower. Not because designers need to become developers, but because understanding implementation helps us understand the structure behind the interface.

When designers understand how components, accessibility patterns, performance constraints, and system architecture work together, they can ask better questions, communicate more effectively with engineers, and make more informed design decisions. Instead of treating engineering as a black box, we begin to see how products are actually built.

Today, open-source projects, public repositories, documentation, and AI-assisted learning have made it easier than ever for designers to explore technical systems. You do not need to become an expert programmer. You only need enough understanding to connect design decisions with implementation realities.

In this talk, I will share lessons from maintaining a design registry, working on accessibility improvements, building agents, collaborating with engineers, and contributing to an open-source healthcare ecosystem. Through these experiences, I’ll show how technical curiosity helped me better understand complex systems and become a more effective designer.

• Why understanding a codebase is a design superpower—not because designers need to code, but because it helps them understand the systems they design.

• The difference between learning to code and understanding how software is built.

• How technical understanding leads to better collaboration between designers and developers.

• How open-source projects provide designers with a unique opportunity to learn from real codebases, discussions, and implementation.

• Real lessons from contributing to an open-source healthcare project, including design systems, accessibility, and maintaining a design registry.

• A practical approach for designers to start exploring technical systems without becoming software engineers.

• How understanding implementation helps designers make more informed, feasible, and system-aware design decisions.