David Reed

The Bridge Package Pattern

Managing your package architecture for a Salesforce platform product is a major challenge not because it’s difficult as such, but because in many cases your decisions must be made very early in the lifecycle of the product and are very difficult or even impossible to change. This challenge is especially prominent when designing extension packages, which build upon existing managed packages. The bridge package pattern is a package architecture that factors dependency into a tiny, minimal second package whose only job is connecting two other packages that are independent of one another. Think of it like a junction object for managed packages.

Publications Round-Up

I’ve been part of a number of articles and presentations over the last few months that have not so far appeared here. Want to catch up with the latest in free and open source Salesforce DevOps? Here’s some pieces I’d love to share.

"What's the best translation of...?"

I’ve launched a new app, Bibliothekai, to help answer this question.

Working with JSON in Apex: A Primer

This post is adapted from a community wiki I created for Salesforce Stack Exchange.

Automate the App Lifecycle with CumulusCI

Recently, I’ve been delighted to visit the Salesforce Developer Groups in Denver, Colorado, where I live, and in Kitchener, Ontario, to talk about Salesforce.org’s Portable Automation toolchain for continuous integration and automation throughout the application lifecycle.