11–18 of 18 posts
And in most shops it will be just like the live coding stuff: a series of trivia questions that the sage interviewer will already know, unlike that hideous rube, the interviewee.
I consider myself a good debugger, but the interview context helped me see some places I could improve my process. I was comfortable in the pdb debugging system, but could improve my ability to steadily narrow down the key buggy line of code in a short amount of time.
Recent similar-ish sort of article that I quite enjoyed, "How to Freaking Find Great Developers By Having Them Read Code"[1]. I really really appreciate having resourceful people about. People who can go hunt for answers, who can explore questions: they are the ones that make excellent fantastic programmers, and people who are fun to engage with & watch go at it. I very much agree there's a huge weakness in drilling…
Yup and I'm not sure if adding a debugger to the mix is actually worth it. Sure, it's closer to the actual day to day work, but a great dev should be able to understand code even without a debugger.
However, a contrary example to your point about being “able to understand code even without a debugger” is using a dev console in web browser to ‘debug’ html/css/js etc. Depending on the role that _could be_ considered an important skill (a specific case being examining http status codes).
i was interviewing junior developers so i wasn't expecting master coders. and in addition to the points mentioned, i was also evaluating their ability to communicate. it worked out very well.
Oddly enough, if we don't do our job, we get fired, just like everyone else. Other businesses actually apply this to their interviews and don't require applicants to demonstrate something utterly bloody trivial, as if they could somehow do their job for a decade and not know the basics.
Invariably, every dev writing these kinds of articles is simply stroking their own way of thinking - usually these discussions do not contain:
a) a modicum of common sense. b) an understanding your brain does not work the way everyone elses does.
Just because you find a certain debugging method works for you, doesn't mean it works for me - your most effective technique is not necessarily my most effective technique, because I don't think the way you do.
Some programmers may be slower at debugging, but faster at determining a good solution to a complex problem. They may be slower at writing Jenkins jobs, but faster at solving Maven problems.