[ojkelly]

Build* in isolation the same way we chunk up server side code and test that in isolation. These are unit tests for UI.

Storybook gives you the framework to run them. Add something like cypress on top and you have the whole testing loop.

Making and updating the components in isolation reduces how much you need to reason about when building highly composable components.

The higher up you go (ie more composition) the less you can do in isolation.

But this is only building, you should design with as full an understanding of the rest of your components. Behaviours need to match, style needs to be consistent.

You don’t build a whole program at once, in the same way you can’t build a whole UI at once. At some point, you focus in on one area.

This because exponentially helpful when you team grows to a size larger than one.

[dmitriid]

> Making and updating the components in isolation reduces how much you need to reason about when building highly composable components.

How do you know they are composable if you make and update them in isolation?