Architecture
A platform that grows with you
Package structure, data model and coding standards your team can build on for years. Dependencies mapped, decisions written down.
Freelance Salesforce architect and developer
Salesforce, carefully prepared.
I'm Alwin van Dijken. For 14 years I've designed and built Salesforce solutions that keep working: Apex, Lightning Web Components, integrations and reusable 2GP packages. For government and enterprise, with no agency in between.
Experience
14 years of Salesforce
Recent engagements. Government and industry, from architecture to the last line of code.
- 2026 – now
Lely
Salesforce Engineer
Event registration, onboarding and integrations for an international maker of agricultural robots.
- 2025 – 2026
Municipality of Almere
Salesforce Technical Architect
Layered fflib architecture, REST, SOAP and Platform Event integrations, Experience Cloud and 2GP packages.
- 2025
Municipality of Tilburg
Senior Salesforce Developer
LWC and Apex in service and domain layers, flows and reporting.
- 2023 – 2025
Municipality of Amsterdam
Senior Salesforce Developer
Citizen contact with Omni-Channel and Knowledge, government data integrations and platform accessibility.
Before that, eight years at BrightFox, for clients including Telfort Business, Medtronic, Exact and teams in the UK.
Mise en place
How I work
In a good kitchen everything is prepared before service starts. I work the same way.
- 01
Understand first
We start with the problem and the people who have it, not with the technology.
- 02
Decisions on paper
Every architecture choice gets a short decision record, so your team knows later why things are the way they are.
- 03
Ship small, ship often
Working software in short steps, with tests and a preview you can check yourself.
- 04
Built to hand over
Code, documentation and standards your team can carry on without me.
Blog
From the kitchen
- I moved my registry into Custom Metadata, then moved it backApplying open/closed by the book made the code worse. When configuration is the wrong tool.
- @isTest doesn't protect you from Type.forNameType.forName still finds an @isTest class and creates a working instance, even outside a test. Why that matters for managed packages, and the fix.
Hire the chef, not the agency
Senior Salesforce architecture and Apex, straight from the person who writes the code.