Design, before Any SoftwareLesson 67 of 74

Module 7 · Making the decision once

Names that survive the next change

In this lesson

  • 8 min read
  • 8 reading sections
  • Knowledge check
  • Lesson 2 of 9 in this chapter

This chapter’s goalConvert a set of one-off screens into named tokens and a small component set, decide for any new element whether it is a variant of something existing or a new thing, specify every state a component can be in, and say at what point a project is large enough for the system to be worth its maintenance cost.

This chapter’s media

The film explains chapter ideas. The audiobook narrates the complete teaching text.

FormatEnglishहिंदी
Chapter filmWatch1:50Not available
Full audiobookNot availableNot available

A little at a time

Explore an idea, try it, then check what stays.

Step 1 of 10Free · no account needed
Lesson steps

The name outlives the value

--colour-red-error is a token that was named twice and will be wrong once. When the error colour becomes orange because red tested badly, the name is a lie that stays in the codebase for years, and every new person has to learn that red means orange here.

The rule is straightforward and the discipline is not: name by role, never by appearance.

Text
Good: --colour-danger        Bad: --colour-red
Good: --colour-surface-raised Bad: --colour-light-grey
Good: --button-primary        Bad: --button-blue
Good: --card-interactive      Bad: --card-with-shadow

The exception is the primitive layer from the previous lesson, which is supposed to describe values, because that is its job. --blue-500 is a correct primitive name and an incorrect semantic one.

Your place and first choices stay on this browser. Classroom credit is recorded separately.

Stuck on something?Ask Meher, your AI tutor

How to cite: Addaly (2026) ‘Names that survive the next change’, in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/naming-things (Accessed: 21 November 2026).