As Salesforce developers, we all too often come across ‘Mondo’ coding patterns in existing Apex classes and triggers. Apex is a fully functional and modern object oriented programming language, yet programmers often fail to utilize its capabilities that allow for well designed clean and segmented code. Instead, they often fall prey to this common yet risky coding approach which typically results in lengthy, overly complex and fragile classes and triggers.
In this presentation, we’ll discuss why it’s important to avoid or refactor away from these ubiquitous ‘Mondo’ coding patterns, and we’ll explore how to embrace the concept of modular development patterns to help isolate, simplify and decouple business logic, resulting in cleaner, more readable and hence more maintainable code.
Along the way, we’ll clarify the difference between Software Frameworks versus Software Design Patterns, review the benefits of a Separation of Concerns development approach, and show how to implement modular architecture in Apex.
We’ll also show how to leverage external micro services running on Heroku that provide extended functionality not available in Apex, and leave attendees with some homework and pointers to documentation, posts, Trailhead content and expert elearning videos for lots of self directed further learning.
