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.
Ben AvelingSpoiler: A coding interview isn't: can you write perfect code.
Well, maybe sometimes it is.
But IME it is at least as much about things like: how do you respond to being corrected when you (inevitably) make a mistake.
@norootcause
Well, maybe sometimes it is.
But IME it is at least as much about things like: how do you respond to being corrected when you (inevitably) make a mistake.
@norootcause
unlofl [Promoted Toot]@BenAveling @norootcause the sane version of all this I've been through was being handed a broken program in a language I didn't know, and told to figure it out.
"Well, the error looks like an HTTP 500, so it reached the server, and I think the request is invalid here, but there should also be a better error from the API, I think the MIME type is wrong but I'd need the API docs"
apparently I nailed that part despite barely knowing js, and its ACTUALLY what responding to incidents is like.
Similar to my experience - the boss wasn't looking for 'did I know everything', but 'how did I react when I didn't know'.