DEV Community

loading...

Discussion on: My Transition from .Net to Salesforce. My thoughts and the challenges so far.

Collapse
manzanit0 profile image
Javier Garcia

Certainly an interesting opinion! In my case, it's been directly the opposite way: After a few years developing on the Salesforce platform, integrating against multiple services and having the fullstack experience of Apex and Lightning Components, I grew tired.

On the one hand, it's true that Salesforce does A LOT for you and that with very little code, a lot of business value is achieved. That, in my opinion, is the true power of the platform. It has frameworks for the frontend that couple perfectly with the backend with little to no work and deployments are much less of an impact than on other platforms.

On the other hand, the development experience is terrible. Debugging long integration queues or triggers which call queueables which make callouts and then trigger other triggers is very complicated. You have to go through long debug logs and place traces everywhere. And then, even the tooling is starting to be better, it is not abundant. I use Illuminated Cloud with IntelliJ, but it's still not the same as Visual Studio. Now, with SFDX, the future looks brighter, but it is not yet mature enough.

At the end of the day, I do agree that it is a very good platform, but for the true developer, it falls short. It's the reason why I started to move towards .NET. The control you have over the application is different :)

Anyways, great article nonetheless! I enjoyed the read :)