How to tackle technical debt in Salesforce?

Technical debt (also known as design debt or code debt) is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.

In Salesforce context

1. Poor Customization(Point and Click and Coding)
2. Bad Configuration(Report, List Views, etc)
3. Bad design and not following standard and best practices

How to overcome?

Following are some possible ways

1. Utilize Salesforce out of box feature rather than building custom solution.

2. Follow Salesforce standard and best practices.

3. Implement exception handling in the code and capture all the exceptions in a Custom object to handle it.

4. Set API usage notification - http://www.infallibletechie.com/2017/04/api-usage-notifications-in-salesforce.html as a proactive step to catch the API limits.

5. Set Up Governor Limit Email Warnings in Salesforce - http://www.infallibletechie.com/2017/04/set-up-governor-limit-email-warnings-in.html.

6. Increase the API version of the component when you get an opportunity to update/enhance it.

7. Use Salesforce Optimizer - http://www.infallibletechie.com/2017/02/salesforce-optimizer.html.

8. Use Code Scanner from Salesforce - http://www.infallibletechie.com/2015/03/how-to-check-code-quality-in-salesforce.html.

7. Use Field Trip AppExchange to find the usage of fields.

8. Use Salesforce Adoption Dashboards AppExchange product to find the user adoption.

9. Develop Test Class to test your code instead of cheating to achieve code coverage.

10. Utilize Trailhead, Release notes from Salesforce, Certifications, etc.

11. Utilize Query Plan for SOQLs - http://www.infallibletechie.com/2015/07/query-plan-in-salesforce.html.

No comments:

Post a Comment