Developer experience matters. Tooling decisions affect productivity, quality, attraction of talent.
Standard stack:
1. IDE.
- VS Code with Salesforce Extensions — most popular, free.
- JetBrains Illuminated Cloud — paid alternative.
- Salesforce Developer Console — fallback for quick fixes.
2. Source control.
- Git — standard. GitHub / GitLab / Bitbucket.
- Branch strategy: trunk-based or Git Flow.
3. CLI.
- Salesforce CLI (`sf`) — orchestration.
- Custom shell scripts for common operations.
4. CI/CD.
- GitHub Actions — popular, free for most usage.
- GitLab CI, Bitbucket Pipelines, CircleCI, Jenkins — alternatives.
- Salesforce DevOps Center — Salesforce-native.
- Gearset / Copado / Salto / AutoRABIT — managed packages with sophisticated features.
5. Testing.
- Apex unit tests (built-in).
- Jest for LWC.
- PMD for static analysis.
- ESLint for JS.
- Salesforce Code Analyzer — integrated linting.
6. Local emulation.
- Scratch orgs for feature work.
- Sandboxes for shared / integration work.
7. Diff / deployment.
- sgd (Salesforce Git Delta) — only deploy changed metadata.
- DevOps Center for declarative deploy.
- Custom scripts for repeatable patterns.
8. Project structure.
- Salesforce DX project format (
sfdx-project.json). - Modular packages (Unlocked Packages).
9. Documentation tooling.
- Confluence / Notion for architecture docs.
- Markdown in Git for code-adjacent docs.
- In-code docstrings for APIs.
Tooling decisions:
- Standardise across team — one IDE, one CI/CD, one source control.
- Automate the boring — pre-commit hooks, automated formatting, automated testing.
- Quality gates in CI — coverage, PMD, ESLint.
- Fast feedback — local testing, scratch orgs.
Investment:
- Tooling time is high-leverage. Saves hours daily.
- Onboarding new devs is faster with good tooling.
- Quality is higher with automated checks.
Common pitfalls:
- Bring-your-own tooling — chaos.
- Manual processes — slow, error-prone.
- No CI — manual deploys forever.
- Inadequate testing — breaks reach production.
Senior architect insight: developer tooling is part of the architecture. Invest deliberately.
The senior framing: the difference between mediocre and great Salesforce orgs is often tooling. Great orgs deploy faster, with fewer defects, and onboard new devs in days. Mediocre orgs deploy slowly, with more issues, and take weeks.
Tooling pays back orders of magnitude.