It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
You didn't mention what benefits led your organization to adopt an interview "code review" process so different from your day-to-day process, what it demonstrates about the candidates, or what insights it offers you into how they think and model and decide. Can you come up with any?
I don't think we had this conversation about the why. I talked to some colleagues about this and I realized that I learn more about ourselves than about the candidates, how we think. Not the point of the interview...
Yeah, I also can't come up with anything this process offers us.
Thanks for the reflection!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You didn't mention what benefits led your organization to adopt an interview "code review" process so different from your day-to-day process, what it demonstrates about the candidates, or what insights it offers you into how they think and model and decide. Can you come up with any?
I can't.
I don't think we had this conversation about the why. I talked to some colleagues about this and I realized that I learn more about ourselves than about the candidates, how we think. Not the point of the interview...
Yeah, I also can't come up with anything this process offers us.
Thanks for the reflection!