Salesforce Developer

Apex Syntax & Primitive Data Types

Why: You handle type conversions and null cases across several classes, so shared utility code does not break a feature built by a teammate.

Collections: List, Set & Map

Why: You pick the right collection to group child records by parent Id, so a rollup across thousands of rows is one pass instead of nested loops.

Governor Limits

Why: You use the Limits class to check headroom and design around CPU and heap pressure before a feature hits them in production.

Bulkification Patterns

Why: You build Map-based result sets and one DML per object, so your trigger holds when a flow and a data load fire it in the same transaction.

Trigger Context Variables

Why: You compare Trigger.oldMap with Trigger.newMap to act only on fields that changed, so an update does not rerun heavy logic for unchanged records.

Trigger Design Patterns (Handler Framework)

Why: You keep one trigger per object that delegates to a handler class, so adding a second requirement does not create a conflict over execution order.

LWC Component Structure (HTML/JS/Meta)

Why: You organise a component bundle with its HTML, JS and meta files correctly, so it deploys and appears on the right page in App Builder.

Reactive Properties: @track, @api & @wire

Why: You decide what to expose with @api and when a field needs tracking, so a parent updates a child component without stale values on screen.