Do you guys like salesforce development?

  • 11
    No. I don't consider it development at all. The development decisions, and interesting problems on platforms like salesforce, SAP, sitecore, etc were done by the team that built the platform. Developers on those platforms are just doing overly complex configuration.
  • 3
  • 5
    Show me one person that genuinely appreciates Salesforce.
  • 0
    This is a joke right? 😂
  • 4
    2 years in and counting.

    @SortOfTested yes and.. no I see your point, I won't argue with that.

    SF devs are more plugin / customisation layer, extending the standard functionality to meet business requirements, this can be interesting with a no-code approach and a royal pain in the ass once you have a large list of customisations and code is both faster and easier to maintain.

    Although the new trigger and scheduled flows in summer 20 are fucking amaze balls.

    You need to plan ahead not just jump in, and you need to know the way the system wants to behave VS the way you need it to behave, and the consequences of introducing anti-patterns. The platform will punish you the more you scale, and this will require heavy refactoring to just be able to maintain a safe state, but I do enjoy the challenges it presents.

    PS: I'm a sucker for punishment 🤤
  • 2
    That just sounds like self-flagellation with extra steps 😋
  • 1
    @SortOfTested I don't know if it's that bad yet, but people do keep calling me a masochist 😅
  • 2
    From my understanding Salesforce is very similar to ServiceNow which has been giving me brain cancer since March.

    I'll tell you rn it ain't development, it is just configuration nonsense and molding a system to fit your company in ways it was never intended to. Sometimes it's okay to change work processes over hacking the system together in bad ways to handle special processes that only are the way they are because "that's how we've always done it" jesus FUCK.

    My blood pressure.
  • 2
    @Elyz @SortOfTested In fairness, Salesforce can (but often doesn't) have genuine development associated with it - custom frontends are written in *reasonably* standard libs these days (UI components aside), and custom backends can be achieved using Apex. Apex sucks balls to be sure, it's akin to a bastardised form of Java 5 - but it is development.

    You *can* do some pretty neat things with it - I've written fully fledged backends with Apex and SOQL that call a whole bunch of web services, perform data aggregation, wrap everything up in JSON for frontend to consume nicely etc. But it's an exercise in frustration, and it feels like you're fighting the platform every step of the way. Plus if you're not careful or don't have a full knowledge of what else is running in your org, the thing will likely be slow, unreliable and buggy as hell as it hits arbitrary limits all over the place.
  • 1
    @SortOfTested Some people even fail to do proper configuration.
    In previous orgs we used Salesforce API but most of the time API returns error response due to improper configuration
  • 2
    @AlmondSauce That's exactly what happened in previous company. 90% of the times bugs occurred in our website is because SF team changed or didn't configure endpoint properly.
Add Comment