High 10 errors Junior Devs do

Are you a Junior dev attempting to get higher?

I’ve been working with lots of Jr devs and thru the time I recognized 10 widespread errors they made.

Learn them and let me know in case you establish with a few of them. However keep in mind

My aim with this listing is that will help you develop into higher than you have been yesterday.

1. Misreading errors.
   This appears to be fairly apparent however it’s wa…y to frequent {that a} dev reaches to me asking for assist as a result of they’re caught …and once I see the error my rapid query is

Did you learn fastidiously the error? In that case what is the error about?

As an example, easy errors (😅) like:
Code Error

After all, there are occasions when the error message just isn’t clear and it is alright to ask for assist, however please learn and attempt to perceive what’s failing.

1. Write code as quickly as doable.
   When you are going to work on the subsequent job, verify in case you begin coding ASAP, as a result of that is one thing it’s best to enhance. There are a lot of issues it’s best to do earlier than hand to be sure you ship what’s anticipated, as an example:

Learn and perceive the scope of the ticket.
Make clear ambiguity along with your Product Proprietor/Staff Lead.
Search for areas within the app that could be impacted or at the least you should check.
And many others

1. Misunderstanding of the ticket’s scope
   This may go in two methods:

Un-fulfillment of all acceptance standards. In different phrases, doing lower than what was anticipated.
Including issues past the scope of the ticket. Doing greater than wanted.

1. Mixing new code with refactors.
   Simply with expertise you’d know the way dangerous is to introduce new code whereas refactoring the identical space.

Goal to ship issues separate and if you wish to refactor some code as a result of it is terrible or another motive, be sure you know the code nicely or at the least have an honest set of checks earlier than doing the refactor.

1. Not taking time to study your tech stack.
   In case you’re new in an organization, it is possibly your first job, you need impress your coworkers, so that you do your finest to ship as many tickets as doable, however in the long term you are not going to extend your velocity and you would be caught with foolish points since you did not study the stack sufficient.

Right here is one the most effective quotes that illustrate the concept.

Give me six hours to cut down a tree and I’ll spend the primary 4 sharpening the axe. — Abraham Lincoln

Take time to study your stack, in case you work with React, learn the documentation & perceive what is going on on, study Javascript nicely, take programs, …continue learning!.

Finally one thing that might take you a few days to finish, you’d have the ability to do it in a matter of hours.

1. Concentrate on supply not on high quality.
   Normally the devs I labored with attempt to end the tickets ASAP and seize the subsequent one. however I all the time inform them:

I want in case you ship one ticket with zero or few bugs as a substitute of delivering 10 tickets filled with bugs.

1. Not asking questions
   First in any respect, in case you work on a spot the place you do not really feel welcome to ask questions it’s best to inform your supervisor or transfer to a unique place.

A whole lot of instances I get into a gathering with the group, we focus on a brand new function and we ask if somebody have any questions and the room goes quiet, so we end the assembly.

However in a while and numerous instances Jr builders ask me instantly questions of issues they did not perceive throughout the assembly.

So I am going forward and clarify to them that asking those self same questions throughout the assembly is extra priceless as a result of we are able to contemplate much more issues and that their enter is all the time welcome.

1. Getting caught
   That is associated to the earlier one, in case you’re caught with a difficulty, it is higher to lift your hand and ask for assist slightly than getting block your complete day.
   However as I stated in level #1, be sure you learn fastidiously the error and if you do not have a clue of how you can resolve it, ask for assist.

2. Having the identical errors on a regular basis.
   If in case you have a difficulty and ask for assist, be sure you study what occur, why it occurred and how you can repair it.

As a result of the subsequent time you face the problem, you possibly can resolve it in personal, and even higher, ultimately you possibly can assist educate somebody what occur, why it occurred and how you can resolve it 🔥.

1. High quality is a QA division responsability.
   It is fairly widespread that builders depend on the QA to ensure that we aren’t introducing bugs or breaking the app.

In case you eliminate that mindset, and begin caring about delivering options with prime quality earlier than they attain the QA individual, you would be miles forward of the others.

Conclusion
You have to be sincere and assess your self. Do not feel ashamed when you’ve got recognized with one, two or all of them.
Everyone was a Jr dev sooner or later and I’ve to confess, I obtained higher at a few of them once I get into Senior positions.

The secret is to establish them and be higher than yesterday ❤️.

I hope you loved! Did you establish with a few of them? Let me know within the feedback

Additionally you possibly can observe me on twitter the place I share extra tricks to develop into a greater dev.