lecture 2 of 160 completed

Structuring a suite four teams share

One folder works for one team. When several teams contribute, structure becomes an ownership question, not a tidiness question.

What you'll learn

  • Why structure becomes an ownership question at scale
  • How to split shared code from team-owned code
  • Which decisions to make before people need them

The intermediate track showed you how to organise a suite by feature. That structure holds until about the point where a second team starts contributing. Then it breaks in a way that has nothing to do with folders.

Here is the failure that follows.

A shared login command lives in support/commands.js. Four teams use it. The payments team needs it to accept a second argument. They add it. Two weeks later the accounts team's suite fails in a way nobody connects to that change, because the person who made it had no idea who else depended on it.

members only

Keep reading with the full course

The Foundations track and the first 5 lectures of each framework are free. This lecture is part of the paid course, which unlocks every lecture, all three frameworks, and downloads.

See the options →