Speaker 2
Okay, that's interesting. I'm kind of curious, like, do you have to write tests or what are kind of degrading criteria on that? First, do
Speaker 1
we hear from them again, because some people they come, we get the test, they never come back. So that's an important criteria, I think, the first one. And then after that, it was more about like all this of the problem, like, like, let's say some people, it was interesting because so it's the first time they have to do something in edX here. And like some people, they will bring just plug, like, and try to do stuff with just plug, try to do like very, very minimal. I think it was a no-get developer. So it tried just to pull like the smallest amount of the possible to make something very minimal. Some people, they will like pull fenix and just do it with fenix. And then I'm not sure like it was about do we understand the code when we read it? It's not like we don't have like a specific grid, like, and like a rate like that. It was a bit, it was startup time. And that's how we we posted that at the time.
Speaker 2
Okay, so it's very much kind of feeling based and just kind of looking at the style and seeing what you can see there, right? Yes. Now, have you ever seen somebody just like completely just go in a whole different way that you're just like, okay, at least he tried, but this is just, it's not going to
Speaker 1
work out. Yeah, actually we saw some code that's quite unwedable, un-maintainable, like, to us just, you know, like, I'm not sure to say that, it was quite hairy, like, difficult to understand what they are doing and like naming of stuff is like a girl, a quail something like be like, oh, difficult to find yourself. But yeah, I guess good naming is important. People
Speaker 2
really do that.