Lorin Hochstein 
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code.
rk: it’s hyphen-minus actuallyI hate live-coding interviews. If someone is watching me, I forget how to even type. Obviously my 30+ years of writing code, all my open source stuff, my extensive resume, all those papers and conference presentations were just me faking it.
Chris Petrilli@rk @norootcause ever since Google made me write code (not pseudo code, not math) on a fucking white board during an staff engineer interview, I have seen them as an indication of pompous douchebags hazing people.
Nobody writes code like that.
I honestly thought people were exaggerating how stupid they were.
meejah@petrillic @rk @norootcause The only interview I almost just walked out on was some dumb "write this in C++ on the whiteboard" which is already monumentally stupid -- but then one of the interviewers was like "you missed some braces here, and here".
That was the last part I really heard ;) since I at least _mentally_ left the interview at that point
@meejah @rk @norootcause I literally looked at them and asked "Can you all not afford computers here?"
@meejah @rk @norootcause and given I was interviewing for a staff security engineer, asking me to write A* on the board for graph search seemed... like have you all not heard of libraries before? Maybe write it once and optimize the hell out of it, rather than having every engineer write their own.
"I didn't know I was interviewing for a foundation algorithm libraries job"
mtnrbq65@petrillic @meejah @rk @norootcause
Great comeback! 😁