The document outlines 10 commandments or best practices for developing on the Salesforce platform: 1. Keep code simple with the KISS principle 2. Avoid putting queries in for loops 3. Avoid putting DML operations in for loops 4. Only have one trigger per object 5. Only put trigger execution logic in triggers 6. Balance clicks vs code for a happy admin and developer 7. Use maps for efficient queries when needed 8. Leverage relationships to reduce queries 9. Aim for 100% test coverage of all code 10. Write meaningful tests that assert expected behavior The document provides guidelines but also notes they can be broken when

1. Apex 10 Commandments
James Loghry
Technical Architect, EDL Consulting
@dancinllama
Kevin Poorman
Principle Architect, EDL Consulting
@CodeFriar

2. James Loghry
Technical Architect

3. Kevin Poorman
Principle Architect

4. Safe Harbor
Safe harbor statement under the Private Securities Litigation ReformAct of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of
the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking
statements we make.All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service
availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future
operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments andcustomer contracts or use of
our services.
The risks and uncertainties referred to above include– but are not limited to – risks associated with developing and delivering new functionality for our service,
new products and services, our new business model, our past operating losses, possible fluctuations in our operating resultsand rate of growth, interruptions or
delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and
acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and
manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization
and selling to larger enterprise customers. Further information on potential factors that could affect the financial resultsof salesforce.com, inc. is included in our
annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and
others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be
delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features thatare currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

5. Commandments 1-5
Kevin Poorman

6. #1 Thou Shalt keep thy code Stupid Simple. (Kiss)

7. #1 Thou Shalt keep thy code Stupid Simple. (Kiss)

8. #2 Thou shalt not put queries in for loops

9. #2 Thou shalt not put queries in for loops

10. #3 Thou shalt not put DML in for loops

11. #3 Thou shalt not put DML in for loops

12. #4 Thou shalt only put one trigger per object

13. #5 Thou shalt not put code in triggers other than calling
methods and managing execution order

14. Commandments 6-10
James Loghry

15. #6 Thou shalt have a happy balance
between clicks & code
– “I get an error saying that I’ve reached the maximum number of workflows”
– Triggers that replicate declarative functionality.
• Roll-up summary
• Workflows
• Flow Triggers
Good Salesforce Architectural Design

16. #7 Thou shalt utilize maps for queries when needed

17. #8 Thou shalt make use of relationships to reduce
queries wherever possible

18. #9 Thou shalt aim for 100% test coverage
In general test your methods for:
 Positive effects.
• Given proper input it should act like this.
• Not just happy path, but all logic branches.
 Negative effects.
• Given bad data it should error like this.
 Role/Profile/User effects
 Given a user with X profile and Y role it should act like this.
 Bulkification
• Load 200 or more records to test limits.

19. #10 Thou shalt write meaningful and useful tests
• Not a test without System.assert calls
• System.assert(A==B)
• System.AssertEquals(A,B)
• System.AssertNotEquals(A,B)
• The more assertions the better.
• Create mock data, never rely on existing production data.
• Test all conditions, not just positive test cases
• Test one criteria per unit test.

23. #Bonus! Thou shalt feel free to break these as
wisdom merits.
After all:
 Sometimes you just need a list of Id’s
 These commandments, despite their name, are guidelines for success,
not syntactical rules you just can’t break.
 Break them if you need to, Adhere if you can – they’ll save you time in
the long run.

24. Questions & Answers