The walkthrough means actually walking through the code. So you're giving somebody a tour through the code from beginning to end.
Because if you have, all you do is highlight, things where you're having problems. The issue with that, unless you're talking to somebody who has a holistic understanding of the system you're talking about, they're going to be lost, as far as they can make suggestions saying, well, it's best practice for Django to do this here, or something like that. But if you walk them through the code from beginning data, and then what you're doing is you're giving them an introduction to the whole, the whole system, and then asking you as you go asking your particular questions. It's a technique that's been used in software development for many years. And it actually has that what I mentioned earlier, that mutual benefit, as you walk somebody through the code, it actually gets clearer in your mind. And then as they are able to, to see things and ask you questions or make comments, it contributes to the conversation. So you get that sort of that self-stimulation part of it. And then you've got the outside set of eyes looking at it. All of those together, usually makes for better code. We would even schedule those… when we were developing systems, we will actually schedule a walkthru meeting. And in the walkthru meeting, somebody would come and they will actually have hard copies of the code and hand them out around the table. And then it was their job to walk the group through the code, and for the group to ask questions and make comments as they went. So it's almost like treating code like a PowerPoint presentation. [from 3/18/22 D4G Meeting notes] |