Let’s continue our look at the sample code in the Apex Quick Start. I’m sure Salesforce would never claim this to be production-quality code, but these snippets are what many developers use as a model for writing their own code. Why not demonstrate really great… Read More »High Quality Apex: Code Review #2
We’re embarking on a project to review Apex code. Writing great code is difficult. The logic must be correct, error conditions have to be considered, it needs to be scalable, and the next developer must be able to understand and extend it. Like any engineering… Read More »High Quality Apex: Code Review #1
There are many options for integrating SfApexDoc into a Visual Studio Code project. This article presents a simple option that will get you generating documentation in no time.
If you’ve ever been surprised to find a problem in Salesforce and realized that it’s been there a while and caused damage – this article is for you. We’ll walk through a method for scheduling unit test runs so that you’ll be notified as soon as any of them fails in the future.
One of the primary sources of software defects is duplication, sometimes referred to as Copy and Paste programming. When code or design is copied into multiple places, it’s only a matter of time before one instance of the code will be modified and the others missed – resulting in defects. Even if a developer does remember to update all instances of the duplicated logic, and manages to do so without typos or other errors, multiple changes take time and effort. An important software development principle is, Don’t Repeat Yourself. This article discusses a simple way to avoid duplication in your Apex code by using “Base” classes.