Salesforce: An Unexpected Journey
Practical Salesforce guidance for wherever you are on the trail, from your first org to production architecture.
The unexpected path behind JamForce
Section titled “The unexpected path behind JamForce”None of this was really the plan. I came to New Zealand for a trip and ended up building a life here. Salesforce arrived in much the same way: I encountered the platform while testing a wider architecture, took a second look, and eventually built a career across development, architecture and governance.
JamForce is where I turn that unexpected path into practical guidance for you. The guides explain how Salesforce works, but they also cover the decisions, limits and production realities that tend to appear after the tutorial ends.
It began as a way of checking my own understanding. Writing a topic up properly is the fastest way I know to find the gaps in it, and a good number of these pages started as me confirming something I thought I already knew. It has since grown into more than sixty guides and articles, covering the platform model, administration, Apex and the developer track, query languages, the product landscape, and the roles people actually hold. More about who writes it, and why.
Two kinds of writing
Section titled “Two kinds of writing”There are two kinds of writing here, and they are meant to be used differently.
The guides teach a subject in orderEach idea rests on the one before it, so the admin and developer paths start with how the platform is put together, and the SOQL guides start with SELECT. Read a collection in sequence, or rejoin it at the stage that matches what you already know.
The articles follow one change through to a decisionYou already work with Salesforce and you have hit one specific thing: a retirement deadline, a feature you are weighing up, a production symptom that makes no sense. Each article carries the date its claims were last checked.
Most people end up using both. The guides give you the model. The articles tell you what just changed and what it will cost you.
Where are you starting from?
Section titled “Where are you starting from?”If you would rather not browse a catalogue, start from the description closest to your situation. Each one opens a structured guide at the point where it will make sense to you, rather than at the beginning of everything.
I'm learning Salesforce development
Start with the same platform fundamentals, then move through administration into Apex, integrations, and the UI frameworks.
I'm an admin moving into code
Move from declarative work to developer thinking, tools, and first coding deliverables with confidence.
I'm a developer going deeper on SOQL
Level up query performance, security, and production-safe patterns for real-world Salesforce development.Latest Salesforce articles
Section titled “Latest Salesforce articles”Each article takes a single release change, integration decision, or production problem and follows it through to what you should actually do about it. Salesforce ships three times a year, so a fair amount of this is working out which announcements deserve your attention now and which can wait until they leave pilot.
Apex Quiddity Explained: What 23 Entry Points Report
Understand what Apex Quiddity tells you, when to use it for routing and logging, and what 23 tested entry points in a real org reveal about its limits.
Salesforce Winter '27: What's New and What's Enforced
What's new in Salesforce Winter '27 beyond Flow: the changes enforced now, the integration deadlines to plan for, and the features worth adopting early.
Salesforce Winter '27 Flow: Testing, Retries, User Context
Salesforce Winter '27 adds Flow test scenarios, record-lock retries, edit history and enforced user context. See what changed and where Apex still wins.
Salesforce SOAP Login & Legacy Auth Retirement Runbook
An architect-level runbook for finding and migrating Salesforce SOAP login() and OAuth username-password integrations before the 2027 retirements.View all Salesforce articles →
Written from real Salesforce work
Section titled “Written from real Salesforce work”JamForce is written independently, from hands-on work in large orgs that have been running long enough to accumulate real consequences, and it is not affiliated with Salesforce. Claims about how Salesforce behaves are checked against first-party sources or verified in an org. The Editorial Policy explains how, along with update dates, corrections, and advertising. Background, certifications, and how to verify them are on the about page.