Started coding at the age of 13, now a professional software engineer and Scrum Master, creating and maintaining enterprise solutions. Eat - Sleep - Code - Lift - Repeat 💪🏾
There is a chance that there a comments like "WTF is this not working, check again" or any links to reference sites you placed in files for future reference. You don't have to remove them, but make sure they are looking good :)
Explain your logics
It is very likely that they spot a loop, a part of your code with some uncommon functions or spread operators and ask you to explain what it does and why you choose to go with that.
Overview
Don't jump straight into the code. Give them a little bird's eye view of your project before you dive into the code. This helps them understand it better and chances are that they were about to ask for your goal with this anyway :)
Started coding at the age of 13, now a professional software engineer and Scrum Master, creating and maintaining enterprise solutions. Eat - Sleep - Code - Lift - Repeat 💪🏾
My advice on this:
check you comments
There is a chance that there a comments like "WTF is this not working, check again" or any links to reference sites you placed in files for future reference. You don't have to remove them, but make sure they are looking good :)
Explain your logics
It is very likely that they spot a loop, a part of your code with some uncommon functions or spread operators and ask you to explain what it does and why you choose to go with that.
Overview
Don't jump straight into the code. Give them a little bird's eye view of your project before you dive into the code. This helps them understand it better and chances are that they were about to ask for your goal with this anyway :)
This is good advice, thank you! Especially the comments, I found quite a few like that. 😅
Glad my comment helped you!
Would love to read an article with a recap of the interview and how it turned out 😊