Running Code and Fixing Bugs
So I can solve unseen meds in ~30 mins (think the uncommon ones) in one submission w/o hints and without using the problem tags. But I need to actually run my code (not dry run) to completely solve the problem in time. Sometimes I might be running my code against my own test cases, find a bug, and spend 10 mins trying to fix it by running more test cases but I do fix it within time. Would interviewers see this as me struggling and start dinging me? Is the expectation is to write bug free code as soon as possible? What should I say if I’m running my tests and trying to fix a bug? Is this bad or am I overreacting? Edit: Not talking about companies that don’t let you run your code like FB and Google LC: 236 (14 easy, 176 medium, 46 hard)
Poll
11 Participants
Select only one answer
This seems normal. I try to split my code into small pieces and test them individually in interviews where I can run my code. By the time I have a working solution, there aren’t bugs that I’m going to notice usually. If there are, I just talk through my problem solving process