Apex Best Practice

Question 1

Code Commenting

Answer 1

• We can reduce the amount of comments we have to write be creating self-documenting code (Code with descriptive method/variable names that allow others to infer their purpose from the name alone)

Question 2

Testing

Answer 2

• Even though we have a test coverage requirement of 75% for Apex code, hitting this floor does not mean that we’ve written good, meaningful tests that will ensure that our code works as expected
• To make sure we’ve created good, meaningful tests, we should adhere to our testing best practices (test single, bulk, positive, negative, and as a restricted user)

Question 3

Modularity

Answer 3

• Writing modular methods (i.e. one method
  for each piece of business logic such as one
  method to handle SOQL queries) is a good
  practice to implement
• We can also achieve modularity by moving
  repetitive code to a single method that can
  be invoked multiple times

Question 4

Bulkify

Answer 4

• Design code that can handle large amounts of records/data

Question 5

Staying within Governor Limits

Answer 5

This can be done by:
- Avoiding SOQL/DML in loops whenever
possible
- Operating on collections of records rather
than individual records
- Invoking asynchronous Apex if we still
think we might run into governor limits
after implementing all of the above

Question 6

Follow Trigger Best Practices

Answer 6

• 1 trigger per object, we can’t guarantee the
  order our triggers execute on the same
  object ahead of time
• Make logicless triggers, move all logic to
  helper/handler method and call that method
• Avoid Recursive triggers
• Bulkify

Question 7

Don’t hardcode Record Ids

Answer 7

• There’s no guarantee that the same record will have the same Id in two different orgs
• Additionally, avoiding hardcoding is a good general principle to have - the more dynamic our code, the better