Engaging

Complex methods are hard to test and maintain, as they have numerous paths that need to be covered. Keeping cyclomatic complexity low makes testing substantially easier.

Complex classes are hard to test and maintain, as they have numerous paths that need to be covered. Keeping cyclomatic complexity low makes testing substantially easier.

As a best practice, pages should always present errors in a friendly manner to the user. Without including certain Visualforce tags, such as apex:pageMessages, apex:messages or apex:message, most warnings and error messages only appear in debug logs, leaving users without proper guidance.

The more methods a class has, the more complex it is. Large classes are often a symptom that something in the code has grown too large to be effectively maintained. Avoiding large classes encourages good design while keeping your code readable and easy to maintain.

Custom fields are a limited resource. Moreover, an excessive number of custom fields may hint at an inadequately designed data model.

Flows are a powerful low-code tool to build custom logic. Avoiding code is generally desirable. However, excessively complex Flows can become too hard to test and maintain. For this reason, past a certain degree of complexity, using Apex is preferable.

Having a long argument list is often a symptom that something in the code has grown so large that it cannot be effectively handled. Limiting the number of arguments or parameters allowed for each method keeps the code easy to read and maintain.

Repeating <apex:form> causes various view state instances to be created for your Visualforce page, making it more likely to hit view state limits. Using only one form helps keep the size of the Visualforce view state lean, reducing loading times and the likelihood of hitting governor limits.