Link practice to capabilities show in this comment. #178
Description
@IanDCarroll and @dcmoore -- revision has been reviewed and edited. A few new comments were added, but this is looking good.
Also @IanDCarroll, we’ll need to link to this as a Supporting Practice on the pages for the 3 capabilities it supports: Code Maintainability, Test Automation,, and Test Data Management.
Here is a quick blurb (3-4 sentences) we could potentially use on those pages to summarize this practice (edit as you see fit, or let me know if it's good to go and I can add it to those pages).
###Build a Monorepo for Local Development
Developers who work with dozens of local micro-repos often encounter duplicated scripts, fuzzy service boundaries, and changes that are out of their control. All of this leads to an uncertain and unproductive workflow. Consolidating many interdependent micro-repos into a single dev monorepo allows teams to experience faster feedback on cross-cutting changes, cleaner service boundaries, and better cross-team collaboration. With monorepos, developers can start coding anywhere without waiting for access approvals or available cloud staging environments.
Originally posted by @ntache-81 in #137 (comment)