6 Tips For Writing Bug-Free Code During An Interview
1. TDD
Writing tests will help you break the problem up, and also make you think about edge cases – and there’s a good chance the interviewer is watching for how you deal with edge cases.
Small functions, also test these small functions.
So if the whole code doesn't work, u can know which part doesn't work.
2. Name Things Well
3. Write Short, Focused Functions
Don’t try to solve the problem in one big block of code. Break it up into sub-problems and write methods to solve each of those.
4. Show and Tell
I ever have by staring at it and hoping something will jump out at me. Use your interviewer.
It also shows them that you understand the problem and your solution, and that you are thinking about things like edge cases.
5. Describe Improvements
If you are short on time and have a great idea for how you could improve your solution, describe it.
They know how to critique their code;
They don’t get too emotionally attached to refactor when it’s needed;
They understand time pressure and know that sometimes, you need to make a trade-off between writing the best code you can and meeting a deadline.
6. Avoid Being Uncomfortable
the less pressure you are under, the less likely you are to make silly mistakes.
Arrive nearby early – but only actually show up 5 or 10 minutes ahead of time. You may need to find somewhere nearby to wait around. If a candidate shows up 30 minutes early, it’s annoying. Don’t start by being annoying.
1. TDD
Writing tests will help you break the problem up, and also make you think about edge cases – and there’s a good chance the interviewer is watching for how you deal with edge cases.
Small functions, also test these small functions.
So if the whole code doesn't work, u can know which part doesn't work.
2. Name Things Well
3. Write Short, Focused Functions
Don’t try to solve the problem in one big block of code. Break it up into sub-problems and write methods to solve each of those.
4. Show and Tell
I ever have by staring at it and hoping something will jump out at me. Use your interviewer.
It also shows them that you understand the problem and your solution, and that you are thinking about things like edge cases.
5. Describe Improvements
If you are short on time and have a great idea for how you could improve your solution, describe it.
They know how to critique their code;
They don’t get too emotionally attached to refactor when it’s needed;
They understand time pressure and know that sometimes, you need to make a trade-off between writing the best code you can and meeting a deadline.
6. Avoid Being Uncomfortable
the less pressure you are under, the less likely you are to make silly mistakes.
Arrive nearby early – but only actually show up 5 or 10 minutes ahead of time. You may need to find somewhere nearby to wait around. If a candidate shows up 30 minutes early, it’s annoying. Don’t start by being annoying.
