So many good points made here. I'm very tempted to send this link to every candidate that has sent a resume that has like 2 lines modified from the resume template they and 60 others used. Distinction, value, & competency are core to evaluation of fit.
What i was doing in SFCC 11 years ? ))) We are bulding storefronts for mid and large clients. But we have almost 0 experience in SF core - classic/lighting. It seems because it was not required by clients, but now we starting working on it and learning. Thank you5 for the points!
It is rare that I've seen any company accept the Salesforce UI as it stands to build things in. LWC is slow and clunky, along with the rest of Lightning. There are a lot of good reasons to build UIs off platform while keeping the platform all out-of-the- box for internal users. I don't know, the database has a big emphasis. Tell me a use case for LWCs and I'll probably tell you why LWCs are suboptimal.
Thanks for mentioning the Report & Dashboard requirement. I like that and I did this most when design an App (at least). This is THE most Question need to ask the stakeholders. Otherwise, after design the data model, building securities, and a lot of integrations, suddenly of nowhere, stakeholders asking for a REPORT those data is never ever been store in Salesforce Database. Yes, we can version our development, but at least it reduces the complexity of the requirement. The more clear we understand the requirement, the more robust and real app, system, solution we can design. Thanks for the other 4 red flags! Super helpful.
Interesting point around 10:15 regarding specialization. Ive found that being a big fish in a small pond will make you very detailed and knowledgeable about certain things, but being in a large team will help you scale your knowledge better and learn best practices really well. David, regarding contributing thoughts/opinions to the team during design meetings, what if I’m just not great at thinking on the spot? lol. Usually the more senior people take charge anyway.
I'm a very slow thinker too. I prep for every meeting, and for design meetings especially, I'll review the design for hours ahead of time. If your team doesn't share designs for review prior to these meetings then your team is probably wasting time going over the basics and not getting deep into the design. If this is the case I'd propose to your leadership that all designs must be shared at least 24h ahead of time. Then make sure to block some time on your calendar to review. Everyone has strengths and weaknesses, it's all about figuring out ways to maximize your strengths and minimize the weaknesses. Moves and counter moves.
@@dvdkliu thanks David. That’s an excellent idea. Otherwise solutioning calls are just high level and people are desperately blurting out whatever they can to sound intelligent lol.
I always appreciate your content, especially these insider perspectives. I’m still not a fan of hiring managers’ “filters,” though. You shouldn’t judge a candidate by his control over his previous/current employer (unless he was senior level), because there are still organizations that restrict the (*euphemism warning*) decision funnel. There are also consultants that leave behind technical debt (speaking from experience 😂)!
No Forward looking statement slide...how can this be a Salesforce video without it? 🤣 Fully agree with this list. Developers that jump to development is a scary stance. Flows are powerful to not use and ignore and almost too powerful that basic admins will cause problems
I reject the notion that flow is a good tool for anything more complicated than a couple form pages. I've never seen one that was as maintainable as a code based equivalent would be, it's a spaghetti mess. Do you know of any complex open source flows that aren't a mess that we can study?
I'm Apex-first and transitioning more of my orgs to Lightning Flows. Ideal use case I've found is for requirements where writing properly structured Apex would be overkill for the need. For example, I have some multi-record operations including cloning child records and using a flow lets me leave the error handling and batching to Lightning. If the data transformations were more complex, the Apex investment would be worth it but given the need, Flow is the ideal tool
Hi, content of great value. I would like to know if it's necessary to have a bachelor degree to land a great job as a junior salesforce developer I am currently taking the Meta Front End Developer Course and then I am thinking to shift to salesForce.
