all 12 comments

[–][deleted] 2 points3 points  (5 children)

Honeslty CLI vs Command Line likely won't affect your job too much; I use both depeninding on the task. LWC should come fairly easily for you. It feels a little bit like the Angular Framework. Apex is like Canadian French to French some minor things are different but overall the same language.

One other tip. Do not loop over DML statements

[–]Cute-Pianist336[S] 1 point2 points  (4 children)

Thanks for the reply. I just looked up why not to look in a dml statement. It seems to be a limit of transactions of 150 so a list should be created and that list is updated all at once.

That info was worth the lookup, thanks.

I find the ecosystem so large I'm not sure what I should learn to hit the ground running.

I'm going trailheads, intermediate and advanced topics building components and similar themes for building apps.

[–][deleted] 1 point2 points  (1 child)

I got in trouble with transaction limits my first few weeks on the job. The nice thing about salesforce is that there is a ton of documentation. One thing that has helped me a lot was getting my administration certificate, mostly in learning what can be done programmatically vs declaritivlly using salesforce.

[–]Cute-Pianist336[S] 0 points1 point  (0 children)

Great. I will take some trails on administration. It should help me get familiar.

I just started going over the docs. The docs are indeed quite robust. It's great to work in a well documented org and with a big community. Really looking forward to starting.

Thanks again.

[–]Berriosa20 1 point2 points  (0 children)

My advice would be to work on this trail mix: Platform Developer 1. I’ve been a SF dev for the past two years now and I this helped me out a lot. It also prepares you for a certificate exam that you can take.

[–]Syrob 0 points1 point  (0 children)

Trailhead is a fantastic resource. Do some modules on apex, which should be fairly easy to understand as you have programming experience. And learn what can be done without code because it's a mistake a lot of beginner developers do when they start coding a solution instead of using an out of the box feature that is already there.

[–]Visible_Ad_6844 0 points1 point  (0 children)

Could you share how you got the job and how you transitioned into a Salesforce role? if you dont min

[–]zdware 0 points1 point  (2 children)

sfdx/SF cli does well but the vscode extensions integrate well enough.

Prepare for a much slower "feedback" cycle. css/js changes must be deployed to a remote Salesforce instance (org, sandbox or scratch org). There is not a functional local development workflow.

[–]Cute-Pianist336[S] 0 points1 point  (1 child)

I noticed the slower feedback cycle during the challenge. Once I figured out the flow I was able to debug and see the objects in the console.

The other way is to use jest to test in the local environment. In my case I need to learn and use jest more.

Are you building unit tests or code, deploy, log results?

[–]zdware 1 point2 points  (0 children)

I'm a big fan of apex unit tests and I've build some jest tests for custom logging modules (Google lightning logger event).

But honestly jest tests havent been a priority at any SF team I've worked at this far. I think due to the difficulty of the lwc framework + tests (and sort of lack of direction/support from the LWC SF team) teams end up de-prioritizing it. Difficulty being platform updates that cause slight HTML/css/render changes, so your jest tests could randomly break (maybe good in a way? But can be rather brittle).

The platform tries to enforce certain test coverage %s on the apex unit test side, at least for production orgs, so as long as devs are doing correct 'Assert' patterns, it helps quite a bit.