10Slide, full framethe concept beat
// apex fundamentals
07 / 12
// 03 · bulkificationThree ways a trigger blows the limit
- 01A query inside the loop
- 02A DML inside the loop
- 03A second trigger on the same object
NSDS
// apex fundamentals
07 / 12
// 03 · bulkificationThree ways a trigger blows the limit
- 01A query inside the loop
- 02A DML inside the loop
- 03A second trigger on the same object
NSDS
For structure, definitions and lists — anything you cannot demonstrate. Built at 1920×1080 so it needs no scaling at all, with the same kicker, heading and mono-index voice as every other surface in the system. Three to five lines, never a paragraph: a slide the viewer has to read is a slide they stop listening during.
11Slide + camera, cornerpresenting
// apex fundamentals
07 / 12
// 03 · bulkificationThree ways a trigger blows the limit
- 01A query inside the loop
- 02A DML inside the loop
NSDS
// apex fundamentals
07 / 12
// 03 · bulkificationThree ways a trigger blows the limit
- 01A query inside the loop
- 02A DML inside the loop
NSDS
The same slide with you on it — for the long explanations. Camera in the same corner it occupies during screen share, so the eye never has to hunt for you between scenes. Drop a line from the slide to keep the bottom-right clear: a slide laid out around the camera beats a camera parked on top of a full one.
12Code, full framereading a snippet
// apex fundamentals
07 / 12
trigger AccountTrigger on Account (after update) {
Set<Id> ids = new Set<Id>();
for (Account a : Trigger.new) ids.add(a.Id);
List<Contact> cs = [SELECT Id FROM Contact WHERE AccountId IN :ids];
update cs;}
One query, outside the loop// the fix
NSDS
// apex fundamentals
07 / 12
trigger AccountTrigger on Account (after update) {
Set<Id> ids = new Set<Id>();
for (Account a : Trigger.new) ids.add(a.Id);
List<Contact> cs = [SELECT Id FROM Contact WHERE AccountId IN :ids];
update cs;}
One query, outside the loop// the fix
NSDS
A prepared snippet, not your editor. Camera off, type at 18–20pt, at most 14 visible lines, and the line under discussion marked with the brand rule — highlighting is how you point without a cursor. Wrap long lines; never scroll sideways. If it does not fit in fourteen lines, teach the shape on a slide first and the code second.
13Code + resultcause and effect
// apex fundamentals
07 / 12
for (Account a : accs) { [SELECT Id FROM Contact ...]}
// debug log101 SOQL queries
- ×System.LimitException
- ×Too many SOQL queries: 101
NSDS
// apex fundamentals
07 / 12
for (Account a : accs) { [SELECT Id FROM Contact ...]}
// debug log101 SOQL queries
- ×System.LimitException
- ×Too many SOQL queries: 101
NSDS
The code that causes it beside the thing it causes. The single most useful frame in technical teaching, and the one most people never build: the mistake and its consequence visible at the same moment, so the viewer does not have to hold one in memory while looking at the other. Keep the split even — the error is not a footnote.