flâneur

Python Monorepo: an Example. Part 1: Structure and Tooling - Tweag

tweag.io · 3,786 words · saved by 1 readers

For a software team to be successful, you need excellent communication. That is why we want to build systems that foster cross-team communication. Using a monorepo is an excellent way to do that. A monorepo provides: Visibility: by seeing the pull requests (PRs) of colleagues, you are easily informed of what other teams are doing. Uniformity: by working in one central repository, it is easier to share the configuration of linters, formatters, etc. This makes it easy to use the same code style and documentation standards. Uniformity smooths the onboarding of newcomers as well as the reassignment of engineers to different internal projects. Easier continuous integration: new code is picked up automatically by CI, without any manual interaction, ensuring uniformity and best practices. Atomic changes: because all libraries and projects are in one place, a large change can be implemented in one PR. This avoids the usual workflow of cascading updates, which causes mistakes to be caught later

Python Monorepo: an Example. Part 1: Structure and Tooling - Tweag News Capabilities Functional Engineering Scalable Builds Open source Technical groups Contributions and projects Haskell Foundation partnership Careers Research Blog Contact Modus Create News Capabilities Functional Engineering Scalable Builds Open source Technical groups Contributions and projects Haskell Foundation partnership Careers Research Blog Contact Modus Create Python Monorepo: an Example. Part 1: Structure and Tooling 4 April 2023 — by Guillaume Desforges , Clément Hurlin  python  monorepo For a software team to be

related reading