Designing for the second version

The first version is a promise. The second version is where you find out what you actually promised.

Most teams design v1 as if it were final, then treat v2 as a redesign. I try to design v1 knowing v2 is coming: keep the schema honest, the components boring, and the naming precise.

That way the second version is an edit, not a rewrite.