4 ms·
> You don't think it would add context and clarity if you took 20 minutes from those activities and devoted them to examining a specimen? Sure. If I had to go
by funkaster 9y ago
> You don't think it would add context and clarity if you took 20 minutes from those activities and devoted them to examining a specimen?
Sure. If I had to go through only a few CVs, maybe. And some times I do that for the ones our recruiters screen. But tbh, looking at github/source code and figuring out something (of value) out of it will be more than 20 min. Instead, maybe a blog post or products portfolios would be way more useful and give me something to ask for details on an actual interview.
> Do you do whiteboard interviews? I've never done one less than an hour, and I think you'd be able to glean quite a bit of the same information by looking through the log.
We do, and let me say that `git log` will absolutely not tell you the same info. One is the final version of a thought process (the log). On an interview, at least for me, the result is only one part of what I'm after. How you get there is way more interesting to me, the questions you ask, etc.
- ibejoeb 9y ago>Instead, maybe a blog post or products portfolios would be way more useful Of course. That's why the author advocates for linking to a specific repo with a readme. >We do, and let me say that `git log` will absolutely not tell you the same info >How you get there is way more interesting to me I get a lot of value from the revision history. To me, that is how you get there. When I see something, and I say, "I wish it was more like..." and a few commits later it is, I know we jibe. Likewise, if it's good, and it's something really novel and clean and clever and I never would have thought of it, that's just gold.