Everybody knows that successfully scaling an engineering team requires major cultural adjustments. What few people know is that scaling an engineering team also entails (surprise, surprise) major engineering challenges. These challenges include puzzles such as: a single repo or multiple repos? how to share code within the team? what is the right procedure for committing changes to shared code? how to manage build dependencies? is it even possible to keep the trunk Green? Should each service provide its peers with a client library to wrap its REST API? (and how thin or fat should this library be?)

In this talk we will dive into these topics, and discuss the trade-offs of various solutions.