7 ms·
None of those apply to their fizzbuzz-level question. I’m guessing you don’t have much experience with front-end code if you think this is Chrome tooling speci
by wild_preference 8y ago
None of those apply to their fizzbuzz-level question.
I’m guessing you don’t have much experience with front-end code if you think this is Chrome tooling specific.
It’s really the equivalent of reading a stack trace to get an idea of where to look instead of wolf-fencing off the bat with println. “I would’ve read the stack trace if I knew you wanted me to!” wouldn’t be a good defense, likewise.
Yes, you can teach someone to read stack traces on the job. If-statements, too. And how to write their first function. But that’s not the skill level you’re always looking for.
- judofyr 8y ago> I’m guessing you don’t have much experience with front-end code Okay. You're guessing wrong. I'm just asking for a bit honesty here. If they start adding console.log everywhere, how about you ask them why they're doing it that way? In a codebase I know nothing about it's not uncommon for me to add some console.log around to see how the code flows. Adding breakpoints isn't efficient when it's being hit 100 of times; reading console.log output can be done quite quickly. Maybe I'm misunderstanding the original test, but I'm just tired of playing these games where a person asks me a question and they're holding off important information that they will use to judge me.
- 0xfeba 8y agoI don't hold off important info. I mean, I won't give the answer but I encourage dialog. And your console.log example is valid, but this isn't the same situation. It's a button press, the fetch call is made. I tell them what it should do, I say I would use the debugger but ask them what they would do.