Type of Technical Debt | Platform Area | Examples | Identified Areas | Link to Detailed Log | |
---|---|---|---|---|---|
Accidental or outdated design tech debt | Declarative Automation | - Workflow rules that can be migrated to Process Builder - Multiple process builders per object (validate if this is justified) - Headless flows |
High | Need to merge Account processes | JIRA-0001 |
Accidental or outdated design tech debt | Programmatic Automation | - Triggers/Apex classes that perform automations that can be achieved in Process Builder (e.g. update child records) - Repetitive apex methods that can be refactored (e.g. different methods that return different fileds from an Account in a SOQL can be refactored to one method that builds the query dynamically) |
Low | ... | ... |
Deliberate tech debt | Triggers | - Logic in triggers | ... | ... | ... |
Deliberate tech debt | Apex | - Writing to a logging object on each error instead of creating a reusable framework that handles error logging. | ... | ... | ... |
Bit rot tech debt | User Interface | - Visualforce page that has been modified and extended multiple times | ... | ... | ... |
Data Model | - Using a custom object to track sales activities and extending the object to eventually mirror the opportunity object capabilities | ... | ... | ... |
Created
May 11, 2020 19:46
-
-
Save zaynelt/5e6d46142d94dc67e91b104abce62ce3 to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment