Salesforce: An Unexpected Journey
Architecting Salesforce, one journey at a time
🧭 Salesforce Developer Journey
Section titled “🧭 Salesforce Developer Journey” Start here: map the whole Developer Journey See how the series fits together, what to read first, and how to move from clicks to code without getting lost.
Platform fundamentals for new builders Get oriented in the org, data model, and everyday navigation so later admin and dev topics land cleanly.
Run a healthier org as an admin Org health and monitoring first; pair with Part 2 for Lightning UI, then automation and change in the follow-on parts.
Open the developer track with confidence Tooling, first deliverables, and the mindset that keeps triggers, tests, and governor limits under control.
AI and your future job as a Salesforce developer Where assistants help, where they mislead, and why design and review matter more when code writes itself.
🔍 SOQL, advanced SOQL, and SOSL
Section titled “🔍 SOQL, advanced SOQL, and SOSL” SOQL without the fear Go from “what fields exist?” to readable queries you can trust in reports, Flow, and Apex.
SOQL when the org gets serious Selectivity, security, dynamic queries, APIs, and the patterns that stop slow jobs and surprise errors.
Search across objects with SOSL When one SOQL query is not enough—learn how SOSL thinks and where it fits next to your SOQL toolkit.
☁️ Salesforce products and roles
Section titled “☁️ Salesforce products and roles” Sales Cloud in plain language A grounded tour of how Sales Cloud is meant to work—then explore the rest of the product articles from the sidebar.
Which hat are you wearing: admin, dev, or architect? Match your day job to the right depth of craft before you dive into the role-specific deep dives.
✍️ Blog
Section titled “✍️ Blog” Cut custom integration code with Named Query API Why this Spring '26 capability replaces a lot of thin Apex REST wrappers, where it fits, and how to roll it out without losing governance.
When platform events quietly hit their delivery limit An incident-driven look at how delivery allocations work, why one open browser tab can drain the quota, and how to design around it.