Anyone who works in the Salesforce ecosystem is familiar with the traditional role breakdown that Salesforce portrays in its marketing and communications — the admin, the architect, the consultant, the marketing specialist and the developer.
Developers in the Salesforce ecosystem have traditionally been what other technology domains would refer to as ‘Full Stack’. The same developer would develop the front end (Visualforce) and back end (Apex Controllers, Triggers, Unit Testing etc). In all the ecosystem, whilst nuanced in its specifics, was relatively simple.
As the platform has matured and expanded, as new front end technologies such as Aura have been introduced, I would suggest that the depth and width of the necessary knowledge to be a Salesforce developer has dramatically changed and expanded.
For senior individuals with years of experiences this may be a reasonable expectation. But for junior individuals, or for those who interests are less or more visual, would we be better served by starting to separate expectations and roles.
Could someone be a Salesforce developer, be fully engaged, but only have a light understanding of Apex?
I’d be interested in your thoughts.