Original article πŸ‘‰ 12 Senior Developer Traits Juniors Need To Master πŸ”₯

1. Focus

Focus means saying no to some things, so we can do others. Ideally, saying no to the things that don’t matter. And saying yes to the stuff that makes a difference. The stuff that moves the boat faster.

We are developer, the damn creative with curious mind. We want to learn everything, we want to try everything. But we have to focus on what we are doing. This is not easy, but we have to learn to say no to ourself.

Side projects

2. Pragmatism

This reminds me about my CTO gesture when answers my question: “It depends” 🀷.

Senior Devs know how to balance best practices and time to market. When to take shortcuts and when not to.

And make sure you leave a comment, note or whatsoever in your code to explain about your decision. Also, don’t forget to put the emoji πŸ™ at the end so your college won’t go crazy with you 🀑

3. Nothing To Prove

You don’t have prove anything to anyone. You don’t need other’s validation. Just deliver the best of your ability, with an open mind to learn and improve.

4. Deliver End-to-end

The #1 reason why companies avoid Junior developers is that they need a lot of external help to get things done. External help means you will be bothering a Senior developer to get your stuff done.

This doesn’t mean you shouldn’t ask for help. Let just ask for thing that you can’t find anywhere else on the internet or it’s project-specific.

In our industry, there is rarely a situation that you completely don’t know how to do something, you can always find 2-3 ways to achieve it. The frequently asked question is “Which one is the best?”, and you likely go ask your senior. The next time you do this, I want you to list out all the options you have, what are the pros and cons of each option, and why you think this is the best option. This will help you to learn and improve your decision-making skill.

Btw, there is a practice called ADR, let’s check it out.

(… to be khΓ΄ng tΓ¬nh iu)