Practices Medium (via Scribe)

Work on features, not repositories  ↦

In response to a recent Twitter poll from Kent C. Dodds, Eric Clemmons shared concerns about how organizational boundaries are impacting where development happens. Kent tweeted…

Hey folks who have a decoupled client-server application (no server rendering, server is just an API server). Where is your client code and server code located? (#)

Together in one repo?
In separate repos?

Eric writes in his response on Medium:

Software is like Jello: poke it in one place, and another place jiggles.

In my experience, a repository should house all of the code necessary to make developing & shipping features relatively frictionless.

This isn’t an exact 1:1, but this was a big part of the reason why Segment transitioned back to a monorepo.


Sign in or Join to comment or subscribe

Player art
  0:00 / 0:00