Eudyptula Challenge Status report
Eudyptula Challenge Status report
Posted Mar 26, 2017 7:42 UTC (Sun) by lkurusa (guest, #97704)In reply to: Eudyptula Challenge Status report by fratti
Parent article: Eudyptula Challenge Status report
Posted Mar 26, 2017 20:34 UTC (Sun)
by jmichels (guest, #98352)
[Link] (5 responses)
First, I've had submissions sit in the queue for a very long time. 6 months was the worst.
Second, I've had too many submissions rejected for not doing it the way one way that little expects. I don't mind doing it the way little wants. The problem is that little doesn't tell you this ahead of time, so it kind of turns into a guessing game. I also get that the point of this is to expose you to different parts of the kernel Api in a guided way. But the guessing, coding, testing, and submitting becomes time consuming and very unsatisfying. Especially when you submit a correct and functional answer only to have it rejected for not being the correct functional submission that little wants.
Posted Mar 27, 2017 9:09 UTC (Mon)
by lkundrak (subscriber, #43452)
[Link]
To me it seems that the slowness of responses and rejections of solutions that work but still need some improvements teaches you patience that is so essential in collaborative software projects. The responses were always rather good; even though sometimes a bit challenging to understand.
As for me I've had great fun doing the challenge and recommend it to everyone. But arm yourself with patience and dedicate time to it, especially if you're not a veteran in the area.
Posted Mar 27, 2017 14:50 UTC (Mon)
by geuder (subscriber, #62854)
[Link] (3 responses)
They say it's a bunch of scripts behind the scenes. So maybe too little human review and as soon as you code a bit different from what the scripts' author expected you will get a reject? Of course formatting that checkpatch.pl does not like should be rejected. But even when checkpatch.pl is happy every programming problem has an infinite number of valid solutions (or at least a very big one for all reasonably practical cases)
Just guessing, no experience.
Of course it happens all the time in development teams, whether open source or not, that the reviewer has some points that the author does not agree with. Either deeming the reviewer's suggestions completely equivalent to the code under review or even worse.
Posted Mar 27, 2017 17:52 UTC (Mon)
by ntnn (guest, #109693)
[Link] (2 responses)
E.g. I send in a solution yesterday night and was at place four. I got the next task today around midday - automated scripts would work a lot faster.
Posted Mar 28, 2017 2:41 UTC (Tue)
by rav (guest, #89256)
[Link] (1 responses)
I'll submit Task 5 tomorrow (when I have access to a USB keyboard, he he he... I've probably revealed too much now).
Posted Mar 28, 2017 10:05 UTC (Tue)
by JacobvonChorus (guest, #109772)
[Link]
Posted Mar 30, 2017 2:37 UTC (Thu)
by ajdlinux (subscriber, #82125)
[Link]
Eudyptula Challenge Status report
Eudyptula Challenge Status report
Eudyptula Challenge Status report
Eudyptula Challenge Status report
Eudyptula Challenge Status report
Eudyptula Challenge Status report
Eudyptula Challenge Status report