- SalesforceChaCha
- Posts
- ๐ Takeaways from a Salesforce TA ๐บ
๐ Takeaways from a Salesforce TA ๐บ
3 things I've learned from architecture consulting
Good morning, Salesforce Nerds! These past few weeks Iโve been spending a little time each day documenting my environment at work. Peeling back layers ๐ง of our application architecture โฆ
Overall itโs been a good thing.๐๏ธ Helping me understand & maintain the system better.
Itโs also exposed some ugly truths. ๐จ
Much of the solution is over-customized, code has been over-engineered, common standards werenโt included in the design or implementation, and tech debt is abound. ๐ญ
This got me thinking ๐ค what our main responsibility is to our client as we implement their technical solutions with Salesforce.

Agenda for today includes
Takeaways from a Salesforce TA
Daily Principle
All the Memes
Takeaways from a Salesforce TA
๐ Apply common patterns
Building software is inherently complex. ๐ตโ๐ซ Add to that complexity a solution that bypasses commonly employed patterns in favor of a design thatโs totally custom ๐ and youโre talking a whole new level of complexity!
Be sure to include an up-front design phase to the things youโre designing. ๐ฏ As you encounter problems to solve ๐๏ธ look into commonly accepted patterns to help guide you to a solution.
Solutions like the ones found in Design Patterns, Enterprise Integration Patterns, or Patterns of Enterprise Application Architecture ๐ are standardized & repeatable across the software engineering industry as a whole.
Architects & devโs will recognize these patterns quickly & be able to support MUCH easier than a completely customized implementation. โค๏ธ
๐ฆ๏ธ Maintainability is critical
One major problem can be when devโs get wrapped up ๐ฏ in focusing too much on the technical implementation and not enough on the actual business problems. ๐๏ธ
This type of behavior can quickly lead to code/solutions/frameworks that only exist within your org and, therefore, nobody else can maintain or support (without a lot of work). ๐๐ซข ๐ฑ
This exposes your team/business to the Hero Antipattern. ๐ฆธ Not a good place to be.
As you design & implement your solutions keep these things in mind to help:
Develop & enforce internal standards/guidelines for your team.
When in doubt opt for simplicity and/or readability.
Adopt a development framework across your team.
๐ Document everything
I cannot stress this enough. ๐ฏ Everything. Every decision. Every solution design. Everything you do. Youโll be grateful you did โ itโs the professional thing to do.
The good news! Since youโre following the first two suggestions on this list then this isnโt so bad. ๐ Youโre mostly documenting business process & exceptions to it.
Spin up a base set of technical documentation on your dev framework, common patterns applied, standards/guidelines followed, etc.. โ๏ธ This documentation can be handed out to each client.
Just add areas to get the edge cases/deviations included in each set of docโs and your clients will love you. ๐
Daily Principle
"Iโve learned to always avoid saying โalwaysโ."
and now....Your Daily Memes



What did you think about today's newsletter? |