3 ms·

Your refusal exposed you as someone with a hubris that's hard to work with. Who doubles down and refuses to budge. That you couldn't yield on such a trivial, m

Your refusal exposed you as someone with a hubris that's hard to work with. Who doubles down and refuses to budge. That you couldn't yield on such a trivial, manufactured matter would make me wonder how you respond in a team environment on real matters in the face of adversity.

eanzenberg 9y ago
When I see someone doing something wrong or poorly I speak up and I speak out. Loading csv using vanilla python is in that boat. Present a good reason why it should be done in vanilla. Otherwise, I won't maintain your code as-is and will refactor it.
- always_good 9y ago
  Sounds like their interview worked and they dodged a bullet.
  - eanzenberg 8y ago
    Worked both ways, I dodged a bullet and am happier in my current position than can be :).
thomascgalvin 8y ago
CSV is really fucking hard to parse. There's tons of edge cases. "I'd just use a well-known, well-tested library" is a very valid answer. One of my go-to questions is "sort this array", and if the candidate types `Arrays.sort(input)` they get bonus points, because it shows they have useful knowledge of the language they'll be writing in.
- always_good 8y ago
  Here's how their scenario would actually play out: > I took my sunglasses off, looked him dead in the eye, > and said "Why? Why write your own method in > a vanilla language? Give me a good reason." Interviewer: "To see how you might approach it." It's a synthetic interview question. Why does it suddenly need to be a production-ready CSV parser? We don't have enough information to say whether these are bad interview questions, and it's really not the point. Maybe the interviewer just wanted to see if you'd use good fd hygiene (`with open('file.txt') as f:`) and that you can stub out some toy parser code and speak of it intelligently. And that you wouldn't throw a fit when asked to write some code that a library like `npm install fizzbuzz` can already solve.
- ascorbic 8y ago
  That's a bit unfair. I agree that Array.sort is the best answer, but array sorting is such a classic interview puzzle that most candidates will expect that that's what you want. So instead of the bonus answer, they'll slog away trying to remember the algorithms that they learnt at uni years ago (or codecademy last month).

eanzenberg 9y ago

When I see someone doing something wrong or poorly I speak up and I speak out. Loading csv using vanilla python is in that boat. Present a good reason why it should be done in vanilla. Otherwise, I won't maintain your code as-is and will refactor it.

always_good 9y ago
Sounds like their interview worked and they dodged a bullet.
- eanzenberg 8y ago
  Worked both ways, I dodged a bullet and am happier in my current position than can be :).

thomascgalvin 8y ago

CSV is really fucking hard to parse. There's tons of edge cases. "I'd just use a well-known, well-tested library" is a very valid answer. One of my go-to questions is "sort this array", and if the candidate types `Arrays.sort(input)` they get bonus points, because it shows they have useful knowledge of the language they'll be writing in.

always_good 8y ago
Here's how their scenario would actually play out: > I took my sunglasses off, looked him dead in the eye, > and said "Why? Why write your own method in > a vanilla language? Give me a good reason." Interviewer: "To see how you might approach it." It's a synthetic interview question. Why does it suddenly need to be a production-ready CSV parser? We don't have enough information to say whether these are bad interview questions, and it's really not the point. Maybe the interviewer just wanted to see if you'd use good fd hygiene (`with open('file.txt') as f:`) and that you can stub out some toy parser code and speak of it intelligently. And that you wouldn't throw a fit when asked to write some code that a library like `npm install fizzbuzz` can already solve.
ascorbic 8y ago
That's a bit unfair. I agree that Array.sort is the best answer, but array sorting is such a classic interview puzzle that most candidates will expect that that's what you want. So instead of the bonus answer, they'll slog away trying to remember the algorithms that they learnt at uni years ago (or codecademy last month).