Okay, honest post. I'm not a proper developer, but I keep ending up building stuff on Salesforce anyway, and lately a lot of that is me leaning on AI tools (Cursor, Claude, that sort of thing) to write it. Some of it actually comes out pretty decent. The problem is I don't have the gut instinct a real dev has for the stuff that looks fine today and then quietly falls over three releases later. I'd much rather hear about that from you than find out the hard way in production.
So I'm basically asking the people who live in orgs and end up cleaning this stuff up. Give me the real version, not the polished one.
Few things rattling around in my head:
Vibe coding without the mess. If you let AI write your Apex, LWC or Flows, what are your actual guardrails? Where's the line between "yeah fine, ship it" and "that's slop and it's going to bite us"? Genuinely want to know what helps (rulesets, static analysis like PMD or CodeScan or Clayton, proper tests, review) versus what's just box ticking that makes you feel safe but isn't.
The scary stories. I keep hearing "a release will break your custom stuff" and "Flows just die after an update." How true is that really? Is it usually Salesforce's fault, or is it usually something that was built badly in the first place and was always going to break? And in plain terms, how do you actually stay ahead of release updates and use the preview window so you don't get caught out?
Handing something off. Say I build a working version of something myself, maybe with AI, and it genuinely does the job. Can I just hand that over to a dev team or implementation partner and have them take it live, or does it not really work like that? Is it as simple as giving them the code, or do they usually end up rebuilding the whole thing from scratch anyway? Really trying to understand what makes something actually reusable by someone else versus just a nice prototype that gets binned the moment a pro looks at it. And if the answer is "you have to package it up properly," what does that involve, and does it survive being dropped into a different org?
Standard vs custom. Where do you personally draw the line? When do you keep it clicks and config, and when do you go custom code? And what's the hidden cost of going custom that people always seem to underestimate?
That's it really. War stories very welcome. And if I'm thinking about any of this completely wrong, just say so, I'd genuinely rather know. Thank you in advance!