Felix
Articles

What a sketchbook taught me about components

1 min read

For a year I drew the same coffee cup every morning. Same cup, same table, ten minutes before opening my laptop. Somewhere around the fortieth drawing I realised I was no longer drawing the cup. I was drawing the few lines that made it a cup.

A spiral sketchbook open on a wooden table
A spiral sketchbook open on a wooden table

Good components work the same way.

Drawing what matters

Early drawings were full of detail: every reflection, every chip in the glaze. They took longer and looked worse. The later ones had maybe a dozen lines, and you could tell instantly what it was.

The first version of most components is the early drawing. It has a prop for everything because we have not yet learned which lines matter.

TSX
// Drawing number three
<Button
  label="Save"
  icon="check"
  iconPosition="left"
  size="md"
  rounded
  shadow
  uppercase={false}
/>

// Drawing number forty
<Button>
  <Check /> Save
</Button>

Repetition reveals the shape

You only find the essential lines by drawing the thing many times. Components are the same: you find the right API by using it in a dozen real places, then deleting everything those places didn't need.

The best API is the one that is left after you stop adding things.

What I do now

  • I build the component three times in three real screens before I generalise it.
  • I write the usage first and the implementation second.
  • I delete props that only one call site uses.

I still draw most mornings. The cup has been replaced by whatever is on the desk. The lesson hasn't changed.

Field Notes

A short letter every few weeks — new essays, small experiments and things worth reading.

1,846 readers already get it. No spam, unsubscribe any time.