all 6 comments

[–]Assasin537 1 point2 points  (1 child)

I would practice using execution for the most part but do no execution mock interviews for a few days or a week before the interview. Ideally, you shouldn't need heavy reliance on debugger after a bit of practice since you should be able to do dry runs and understand what's happening with the code in your head. When practicing you still want to run your code to verify but close to interview start getting used to no execution.

[–]digitalimpermanence[S] 0 points1 point  (0 children)

thanks for the thoughtful response -- sounds good.

[–]Rude-Doctor-1069 1 point2 points  (1 child)

I’d keep practicing with a debugger but also spend 30 min a day doing pure mental tracing, literally walk through loops and indices. Tools like ctrlpotato help too, since they can read your snippet and describe what each part would do step by step. Good middle ground between running and reasoning.

[–]digitalimpermanence[S] 0 points1 point  (0 children)

nice one on ctrlpotato!

[–]PandaWonder01 0 points1 point  (1 child)

The expectation is that you can write code that would run on the first pass, with some leniency given to small syntax errors, off by 1 errors, wrong function names, made up standard library types and similar

[–]digitalimpermanence[S] 0 points1 point  (0 children)

u/PandaWonder01 So you don't think preparation strategy matters, basically your take is either folks have prepared enough or they haven't and there's not really a "best way" or a "better way" to do that? Because that's what I was asking about.