Apex & LWC Development
Custom Salesforce code should be boring to maintain. I write Apex and Lightning Web Components that follow platform limits, are covered by tests that check behaviour, and can be read by the next developer.
What's included
- Apex triggers with a clear handler pattern
- Batch, queueable and scheduled Apex for large data volumes
- Lightning Web Components with proper state and error handling
- Aura-to-LWC migration of legacy components
- SOQL and SOSL performance and governor limit fixes
- Apex unit tests that assert behaviour, not just coverage
How I work
Read before writing
I review the existing triggers, flows and components first, to avoid adding another layer of conflicting automation.
Design for limits
Bulk-safe patterns and async processing are planned up front instead of patched in after a limit error.
Test what matters
Tests cover the business rules and failure cases, so refactoring later is safe.
When this is the right fit
- A trigger or flow has become slow, recursive or hard to reason about
- You hit governor limits when loading or updating large record sets
- Standard components cannot deliver the screen or behaviour you need
- Legacy Aura components need to move to LWC
Common questions.
Do you write the tests too?
Yes. Code is delivered with Apex tests that check actual behaviour, not only enough coverage to deploy.
Can you work with an existing development team?
Yes. I can join an existing team, follow its conventions and review or extend its code.
Let's talk about your project.
Tell me what you are trying to fix or build. I respond within one business day.