I was tricked into doing SFDC development for a while, about eight years ago. I had a background in more “traditional” application development: Java on the bac

I was tricked into doing SFDC development for a while, about eight years ago. I had a background in more “traditional” application development: Java on the back end and Javascript on the front end. Working in Salesforce was honestly a pretty miserable experience. Everything you do in it is metered; you have a limit on the number of DB calls you can make in an hour, a limit on how many bytes you can access in an hour, a limit on how many rows you can save… it’s almost as bad as AWS, but nowhere near as manageable because you can’t tell if you’re going to hit a limit until you hit it in production. At least back then, there was no interactive debugger for Apex, and no test client for SOQL (their “almost SQL but not SQL” query language), so any debugging you wanted to do was done using print statements. And of course, you couldn’t run anything locally - everything had to be copied up to their servers in order to something as trivial as test a form validation. I slogged through it for about 3 years before I finally gave up on it - although it does a good job of making simple things like creating input forms for database object easy, it makes harder things like an actual business workflow impossible (it’s noteworthy that even the CRM functionality wasn’t implemented in “pure” Apex/VisualForce because it was too limiting even for the thing that Salesforce was designed for).