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.
🇺🇦 haxadecimal 🚫👑@rk @norootcause
I once was interviewed and asked to write a C function on a provided blank sheet of paper. The interviewer left the room for fifteen minutes. It took me less than five. He came back, said the code looked good, and was astounded: "You even wrote comments!" I had included comments on input parameter requirements and boundary conditions.
The other interviews at that company went well, but the company made me a ridiculously low-ball offer.
I once was interviewed and asked to write a C function on a provided blank sheet of paper. The interviewer left the room for fifteen minutes. It took me less than five. He came back, said the code looked good, and was astounded: "You even wrote comments!" I had included comments on input parameter requirements and boundary conditions.
The other interviews at that company went well, but the company made me a ridiculously low-ball offer.