With the recent release of Salesforce DX and the package development model it got me thinking how to avoid dependencies so I can isolate my packages. Business case The major pain point I saw in the past was around "how to split the metadata so separated teams can work in parallel". For instance, a team can be one line of business or a stream in a project or a feature. In the old monologic development approach (AKA "the happy soup") we used to have these big merge sessions in order to integrate and some times re-write incompatible solutions written in parallel by separated teams (I won't miss those long nights with cold pizza) . Due to several comments of the merge complexity, Salesforce decided to invest in a better way to allow teams to split their work and this is where the new unlocked packages come into place. However, in order to fully benefit from the advantages of unlocked packages we have to deal with dependencies between pack
From Click to Code: Good Practices and tips.