// S-02
Apex architecture
Controller–Service–Selector, coding standards and code review.
// what it is
Apex architecture is how the code in an org is laid out: where the logic lives, how it reaches data and how it is tested.
I work to the Controller–Service–Selector pattern with an emphasis on simplicity (KISS), so the next developer can find things and change them safely.
// when a team needs it
- The codebase has grown without a shared structure and changes are getting risky.
- A growing team needs agreed standards and consistent code review.
- You have architecture decisions to make and want an experienced engineer to lead them.
// what you get
- Apex and LWC coding standards built on Controller–Service–Selector.
- Code review against those standards.
- Architecture decisions documented for technical and non-technical stakeholders.
- Mentoring for the developers who will maintain the code.
// where I've done this
- Hargreaves LansdownEstablished Apex and LWC best-practice guidelines built on the Controller–Service–Selector pattern, reinforced through code reviews.
- Hargreaves LansdownLed technical architecture decisions for the Salesforce practice, documenting designs and guiding technical and non-technical stakeholders.
- CertiniaProvided architectural guidance across teams on scalability, compatibility and reusability, while mentoring engineers.
// contact
Available for contract work alongside a full-time role.
UK / Remote