Our head of customer support:
We are transitioning from using Zendesk to Salesforce. We need to do some dev integrations..

Me:
HELL NO!

You could do that and not write a single line of code on the Salesforce side, ah the things you can do with Salesforce.

Good luck if you haven't jumped into SF before, it's a wild ride.

@C0D4 tell me more? You mean like using Zapier?

@ankitdce Salesforce has a lot of no-code tooling, and almost all of its objects (think Database tables) have a standard API for CRUD - concurrency is a bitch though and it doesn't handle that well for api usage.

Otherwise you can use Apex ( Java ) to extend the platforms functionality with code.

I worked support for a really large tech company.

I always suggested that we straight up didn't need to integrate our tools with the engineering teams. Support was support and engineering was engineering.

Support had their CRM tool and Engineering their numerous engineering tools. Engineering could see our tools as needed, we could see some of their tools

The reason nobody wanted to do it was that fighting with our own internal Salesforce morons (nothing personal to folks who are good at it) was so hard we just didn't want to tackle it and have that many different interests trying to influence things.

If the two groups ever agreed on one thing, that was it.

For those reading along: if you know me at all, you know I'm not exactly a noob. That being said, SalesForce makes you question your own abilities as a coder. Easily one of the hairiest, most incredibly complex (in the worst way) behemoths I've come across.

For those who have experienced Magento programming circa 2010 (not sure if it's improved since), it's about 10x worse than that.

@junon I think that's why it works for me, I'm a sucker for pain and the challenge of chaos is satisfying when you beat it to a pulp.