And so we wondered within thoughtbot, we have all these different people who've come up with their own experience. And as you build experience, you tend to start becoming a little bit more methodical because you've seen what works and what doesn't. And when you're more junior, a lot of that is just random stuff and changing random lines of code and maybe copying something from the internet and hoping things go well. Many of us our experience with debugging has been very much just learning on the job and picking it up by osmosis and trial and error. It's a thing that, as developers, we do all the time, and it's not something that's often taught explicitly. And there was a conversation that got started about how we could get better at debugging. JOËL: Within thoughtbot, we spend a lot of time trying to improve ourselves, improve the broader community as well. But before we go there, what prompted this conversation and then led to the creation of the series? I'd love to know how you went about that research. And then also you mentioned all the research. STEPH: I'm really curious what prompted y'all to start talking about debugging? I'm really excited to talk about the specific topics that are included in the series. And then, starting in April and through the middle of the summer, we are publishing an article every week on the topic of debugging and exploring different aspects of it. We spent about three months doing research, conducting a bunch of interviews, and gathering a lot of material on debugging. This has been a project that we've been doing for a little while. But in addition to spending your time bug hunting with me on this project, I understand that you and other thoughtboters, Jesse Bailey and Louis Antonopoulos, have been publishing weekly blog posts specifically about debugging. In fact, if I look back at my developer journal, the last five or so of my entries begin with a very cheesy mystery title that's like the case of the missing data or Harry Potter and the chamber of errors. And during the past few weeks, we have encountered some very challenging bugs. STEPH: So, Joël, you and I are on the same client project. Joining us is Joël Quenneville, a thoughtbot developer extraordinaire and a previous Bike Shed guest. So, hey Chris, today is an extra special day as we have a guest today. STEPH: And together, we're here to share a bit of what we've learned along the way. STEPH: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. But now that we know your name, I'm so excited to have you on the team and to know who is on the other side of these, hopefully not too nonsensical recordings. In the last recording that will be going through you, I was referring to you indirectly as our next producer. So I will try very hard to do that because I will likely still talk to Thom. So as we run into blunders, which we never do, but if we do, then we can talk to Mandy and ask her to edit things for us. And then who will be editing this episode will be Mandy. Joël Quenneville on the thoughtbot blog post.Chelsea Troy - PoSD 2: What causes insidious bugs?.Joël is helping publish a weekly debugging blog series and in this conversation they discuss how the series got started, technology agnostic debugging strategies, writing less bug-prone software, and speculate if Joël moonlights as a hockey coach. On this week's episode, Steph and Chris are joined by fellow thoughtbotter, Joël Quenneville, to discuss all things debugging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |