The Apex mistakes I still see in every org
Fifteen years of the same five mistakes: queries in loops, tests without assertions, triggers with opinions, hardcoded Ids, and empty catch blocks.
Fifteen years of the same five mistakes: queries in loops, tests without assertions, triggers with opinions, hardcoded Ids, and empty catch blocks.
Business Basics
Your after-update updates the record, which fires your after-update. Breaking the loop without breaking legitimate re-entry.
Business Basics
Triggers receive up to 200 records at once. Every query and DML statement inside a loop is a countdown to 'Too many SOQL queries: 101'.
Business Basics
One method per event, a static bypass flag, and constructor-free classes your tests will thank you for.
Business Basics
Two triggers on one object run in an order Salesforce refuses to promise. The fix is a rule, not a framework.
Business Basics
A business solves a problem for money. Learn what that really means, how it worked before computers, and why the definition has never changed.
Standalone walkthroughs get their own home at /videos/ — with chapter navigation on longer recordings.
| Time | Chapter |
|---|---|
| 00:00 | The requirements, in plain words |
| 03:15 | Standard |
Watch a real data model take shape: objects, relationship choices argued out loud, and the junction object that saves the design.
Six hundred pages of release notes, reduced to the eleven changes that will actually touch your org — and the two that might break it.
Twelve questions covering the whole course. Pass this and your first real trigger is next week's problem.
75% coverage is the law, but coverage is not the point — assertions are. Write a test that would actually catch a bug.