Quality feedback is an essential part of professional growth and we love sharing it not only within our team but also with candidates who get interviewed.
It is a bad habit to send a screenshot with the text “I have an error here.” Instead, you can send an error message and write: “I’m rebasing and have resolved the conflicts but the git says that something needs to be committed while there’s nothing to commit.
You can watch a video about shell on datarockets YouTube.Ask for help properly and describe the problem in wordsJunior developers often share many lines of code to chat or, much worse, a screenshot, with the comment “it doesn’t work, can we have a call”.
In such situations, it is impossible to help without a call and a pair debugging session.
When you describe the problem in words, sometimes it happens that a good assumption about the problem’s cause pops up in your head and you may realize how to fix the problem yourself.Learn how to deal with errors and problemsIf you don’t understand how something works, read the error message, see exactly where it occurred, try to isolate it so you know exactly which piece of code is causing the error.
Even though it might work sometimes it’s hard to learn from this experience and we may leave some hidden bugs unfixed.Ideally, for every single word in the code you write, you should be able to answer why you wrote it.