paired programming while we just sit here and not help at fucking all which is totally how that works in the real world where two other coders watch you and you fucking freak out. fuck this.

@roxie *hugs*

If they treated you like that in the interview, they'd have treated you worse in the job

@roxie Fucksake. I’m sorry

@roxie **hug** Mmm, so, so many interviewers are utterly oblivious to just how much of an obstacle their process can present, even if *they* would feel fine undergoing it. That doesn't mean not ensuring people have the skills you're looking for; but it does mean being a lot more careful in an interview process' design than piling up some interviews and pair-programming and/or timed keylogged tests.

I once crashed out of an interview because of a "write this code whille you're on the phone with me and speak the code you'd write" test. He attempted to defend it on the basis that, oh, well, that's the kind of stress you'll be under at a startup.

The fuck it is. Yes, there can be crunch times, but that's a very different, transient matter. Plus, then, you've got *momentum* - you know the project, the code, the people you're working with, and your life is (hopefully) more or less fine, with a place of your own, or a room somewhere you like, with bills paid. Some or *all* of these may not be true for the applicant. The process must be designed with that in mind, else a company's throwing people aside who'd otherwise do very well.