042: SalesforceDX Architecture Considerations with John Daniel

<p><span style="font-weight: 400;">John Daniel is a Salesforce architect for the B3 group. Even before working with Salesforce, he had encountered programs that had constant issues and technical debt. He found that Salesforce projects brought unique challenges when it comes to designing at the org level and maintaining properly divided applications that respect a separation of concerns. </span></p> <p><span style="font-weight: 400;">John was also part of the group of developers who brought about the first-ever Salesforce DX implementations. Today, we’re talking about his experiences using Salesforce DX for technical architecture. </span></p> <p> </p> <p><strong>Show Highlights:</strong></p> <ul> <li style="font-weight: 400;"><span style="font-weight: 400;">What happy soup is and why it’s a favorite among the Salesforce community.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">What vertical slicing the next phase, horizontal slicing, are.</span></li> <li style="font-weight: 400;"><span style= "font-weight: 400;">John’s styles and suggestions for naming apex classes, Visualforce pages, and lightning web components.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">How he handles things that are dependent upon each other.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">How functional aspects play into the declarative side of the veil.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">What the open-source group is and what it does.</span></li> </ul> <p> </p> <p><strong>Links</strong></p> <ol> <li style="font-weight: 400;"><strong>Twitter account</strong><span style="font-weight: 400;">:</span> <a href= "https://twitter.com/ImJohnMDaniel"><span style= "font-weight: 400;">@ImJohnMDaniel</span></a></li> <li style="font-weight: 400;"><strong>Linkedin account</strong><span style="font-weight: 400;">:</span> <a href= "https://www.linkedin.com/in/imjohnmdaniel/"><span style= "font-weight: 400;">https://www.linkedin.com/in/im