๐Ÿ’ƒ 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โ€™."

Martin Fowler

and now....Your Daily Memes

What did you think about today's newsletter?

Login or Subscribe to participate in polls.