So if we do it as a two-step to do it for ourselves first, and then we'll do it for ICT4D. And I even view doing it for ICT4D as a Public Test prime that then moves on to the actual focus group demos. So we do that type of sequence. And, we're stepwise refining, as we go. Okay? And that way, you don't have to put all your bets on getting everything ready and right for the ICT4D. You get the things you think we're going to need to do for the D4G beta test. Then we will do ICT4D, then we'll do focus groups.
So again, the concept of stepwise refinement is that as we go in time, and as we go into versions of this, things further improve, right? We don't hit perfection from the beginning. Sometimes developers say, how can we use what's called the “brute force” method, to force the right answer in this, and we’ll hard-code it so that it works for the demo. Right? And that's okay. Sometimes you have to do that. But then one hopes that each step, refinement becomes ever fine. And so we look at it, and then again, that question of not only for the next cohort, but for the stranger that comes to the system, how changeable do we make it if making a change means we have to rewrite a chunk of everything? Wow, that's a really expensive system to change. Right? So, gaining maintainability is another aspect of stepwise refinement. [1/4/22, 3/18/22 D4G Meeting notes |