Luke Stutters

And obviously, you don't want to be, you know, at the edge of your ability all the time. You want to kind of line up the nice, easy jobs or things tend to go disastrously wrong. But one thing I have found is that, you know, when you're doing these really hard problems and you're like, can we do it? You know, is it possible? You always have to come back and redo it.

And obviously, you don't want to be, you know, at the edge of your ability all the time. You want to kind of line up the nice, easy jobs or things tend to go disastrously wrong. But one thing I have found is that, you know, when you're doing these really hard problems and you're like, can we do it? You know, is it possible? You always have to come back and redo it.

Once you prove that it's possible, then you have to hit it again, and then you come up to the one. So all of the stuff I've done in a kind of state of intense concentration tends to get thrown away. But it moves you forward down the road.

Once you prove that it's possible, then you have to hit it again, and then you come up to the one. So all of the stuff I've done in a kind of state of intense concentration tends to get thrown away. But it moves you forward down the road.

It breaks my heart every time. Every time I have a git commit with kind of more lines removed than added. Oh, man.

It breaks my heart every time. Every time I have a git commit with kind of more lines removed than added. Oh, man.

Right? I know some people like to take the code out and they're like, oh, I go knocked out, you know, loads of that repeated code. I just think, why couldn't I get it right the first time?

Right? I know some people like to take the code out and they're like, oh, I go knocked out, you know, loads of that repeated code. I just think, why couldn't I get it right the first time?

That is very, very sensible advice. Very sensible advice. And by that standard, I've got amazing at coding over the years. The context is a big mistake. Now, just to be clear, this big mistake has had a happy ending. So this isn't the kind of big mistake I got fired. This is big mistake. We pulled through it and it all worked out. Am I right?

That is very, very sensible advice. Very sensible advice. And by that standard, I've got amazing at coding over the years. The context is a big mistake. Now, just to be clear, this big mistake has had a happy ending. So this isn't the kind of big mistake I got fired. This is big mistake. We pulled through it and it all worked out. Am I right?

Speaking of interviews, I see a smooth transition there. Speaking of interviews, I understand that you have a project which you call Mina Swan interviewing. I have no idea what Mina Swan sounds like. I see a lot of people saying it in the Ruby community, but it's one of these weird in-jokes I think they have in the Ruby community.

Speaking of interviews, I see a smooth transition there. Speaking of interviews, I understand that you have a project which you call Mina Swan interviewing. I have no idea what Mina Swan sounds like. I see a lot of people saying it in the Ruby community, but it's one of these weird in-jokes I think they have in the Ruby community.

Yeah, what a best thing about Ruby's community. It's a really great language and it's a really strong community, really great events, even though obviously the events this year have been a bit difficult. So how are you carrying that culture, that tradition over into the interviewing process? What's your gambit?

Yeah, what a best thing about Ruby's community. It's a really great language and it's a really strong community, really great events, even though obviously the events this year have been a bit difficult. So how are you carrying that culture, that tradition over into the interviewing process? What's your gambit?

That is certainly not the current approach to coding interviews. I've been hearing recently more people talking about how to make coding interviews harder. If you go on something like Hacker News, you know, they discuss which

That is certainly not the current approach to coding interviews. I've been hearing recently more people talking about how to make coding interviews harder. If you go on something like Hacker News, you know, they discuss which

framework they need to insert under the fingernails of potential applicants and i hear if you go to facebook now and apply for a job then they uh you have to bring along your phd in computer science they uh then burn it in front of you mix it into old coffee and make you drink it as part of the interview process so it's really i think it's really something that the tech community needs we have been doing a few episodes about trying to make community more inclusive trying to bring in people trying to keep people in

framework they need to insert under the fingernails of potential applicants and i hear if you go to facebook now and apply for a job then they uh you have to bring along your phd in computer science they uh then burn it in front of you mix it into old coffee and make you drink it as part of the interview process so it's really i think it's really something that the tech community needs we have been doing a few episodes about trying to make community more inclusive trying to bring in people trying to keep people in

And that sounds like a really great idea for a talk. You know, why don't we be nicer to people, try and get the most out of them during interviews instead of subjecting them to torture?

And that sounds like a really great idea for a talk. You know, why don't we be nicer to people, try and get the most out of them during interviews instead of subjecting them to torture?