How to become a strong Salesforce Engineer: 8 Tips from the Routine Automation Founder 2 min 05.07.2022

Even if you have already become a Salesforce engineer or are about to become one, a few tips can help you out whether you think you need them or not. Tips from our Founder can provide you with motivation, inspiration, and a little extra knowledge to get things moving. 

It’s just a matter of habit to bring some automation into your head.   

Do not be lazy, stay in a training memory mood.    

To write the code with ease. In Vs Code, you can write the code fast and more effectively than in Dev Console e.g. 

When you already have deep expertise, you can start to suppress different opinions far from yours. It’s fundamental to accept clients’ feedback and implement all necessary changes. 

Especially during the first year. Presumably to work harder than the company asks. In the first stage, you are investing in yourself in your expertise to work faster in the future.    

Do not rewrite. It doesn’t work like this. The client has tested that functionality, but you will not be able to rewrite the code – there is no time for it. The evaluation always includes time to write code once, not 10 times of the same working code.

If you send the code with errors to testing, be ready to do it over. So, stay self-sufficient, and find your solution to make it fast and effective. Talking about my approach, I prefer to write the unit tests on each bug. Firstly, there will be coverage, and secondly, there will be working test scenarios.   

Draw inspiration from seeing the happy client’s eyes. You have common goals and it’s your job to make things right.