Many are really happy with the progress they’ve made thus far.īut Git can be difficult. Most have already started to use Git and have adopted a Git workflow. In our first two weeks of work, we’ve spoken to nearly 30 Salesforce development teams across the world.
UPDATE SOURCETREE CODE
It makes code clobbering much less likely. Git solves a lot of problems associated with Salesforce development. That said, one still needs to use Git to solve some of the workflow issues associated with continuous development (aka continuous delivery or integration). The platform enables people to build great applications without spending a lot of time at the command line or even in an IDE.
One of the best things about the Salesforce development platform and it’s broad array of tools (Apex, Visualforce, and Lightning components, etc.) is that you can do an awful lot without writing code from scratch.
There are many different types of folks who can contribute to a Salesforce Org: developers, admins, business analysts, sales operations folks, consultants, and so on. The Salesforce developer community is amazingly diverse. Even for those that do spend a lot of time at the command line, they may find Git’s workflows to be confusing to visualize. But there is an elephant in the room: Git isn’t always all that easy to use, particularly if you don’t spend most of your day at the command line.