<div dir="auto"><div dir="auto">Hi,</div><div dir="auto"><br></div>I am sure that if your goal is not to game the system you will write 2000 LOC in at least 20 days no problem.<div dir="auto"><br></div><div dir="auto">Any objectively quantifiable metric one would choose for this would be artificial.</div><div dir="auto">It isn't even clear whether the metric should measure your effort or the quality of your work. </div><div dir="auto">Both of these are hard to even define properly, not to mention the difficulty of finding easily testable tools to measure them with.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 21 Oct 2020, 00:11 Tomáš KubÃÄek, <<a href="mailto:tomas.kubicek69@gmail.com">tomas.kubicek69@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would add one more thing to those points. Point per 100 lines of code will in my opinion encourage us to write ugly looking code, because why would we write something compact and easy to understand when we will get penalized for that.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 20 Oct 2020 at 23:28, Petr Tlapa <<a href="mailto:tlapik123@gmail.com" target="_blank" rel="noreferrer">tlapik123@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">I agree, I think these points you mentioned are quite solid and a really good ground for some kind of discussion. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">út 20. 10. 2020 v 23:02 odesÃlatel Tomáš KubÃÄek <<a href="mailto:tomas.kubicek69@gmail.com" target="_blank" rel="noreferrer">tomas.kubicek69@gmail.com</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I have similar doubts about this system and would appreciate discussion about this topic.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 20 Oct 2020 at 22:26, OndÅej RoztoÄil <<a href="mailto:roztocil@outlook.com" target="_blank" rel="noreferrer">roztocil@outlook.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
Hi,</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
the mailing list seems to be quiet lately. I would like to use this opportunity to post some questions and unsolicited critical thoughts about the concept of 'Project Activity Points' (see 00-common.md in grading repo) which is going to be relevant for students
soon. I understand that the teachers have thought about this more than I have, so they probably had their reasons for setting the rules like this. However, I expect more students to have similar doubts and it might be useful to have some discussion to dispel
these doubts.</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
I will try to be brief:</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
1) Using number of days on which students make a commit as a metric for points seems rather unfriendly towards their schedules. If a student communicates and plans with their team well, I don't see why they should be penalized for only having time to work on
the assignments once a week, rather than twice a week, for example. This can of course be "gamed", but that seems silly and promotes bad Git practices.<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
2) Number of submitted lines of code is also a questionable metric. Generally, the shorter the code is (while retaining readability, etc.) the better. Or do you expect that everyone will need to write 2000+ LOCs anyway? Further, how does it work with Git history
and what code is actually taken into question? Should teammates refrain from refactoring each other's code or they risk taking away their points?<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
3) Finally, more theoretical point. Maybe I am missing why there are teams for this course in the first place, but it seems to me that these 'Activity' rules teach the wrong lesson about team development: that writing code is the only valuable thing a person
can do. Research, design, all sorts of communication - to give few examples relevant even for our limited project - are just as important as coding. Has a system without artificial metrics, where it is solely up to the teams to make sure everyone does a fair
share of work, been tried in the past and it proved too problematic?</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
Sorry for not structuring this better and sorry to my teammates if I tanked our chances for passing the course.</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
Best regards</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">
OndÅej<br>
</div>
</div>
_______________________________________________<br>
NSWI004 mailing list<br>
<a href="mailto:NSWI004@d3s.mff.cuni.cz" target="_blank" rel="noreferrer">NSWI004@d3s.mff.cuni.cz</a><br>
<a href="https://d3s.mff.cuni.cz/mailman/listinfo/nswi004" rel="noreferrer noreferrer" target="_blank">https://d3s.mff.cuni.cz/mailman/listinfo/nswi004</a><br>
</blockquote></div>
_______________________________________________<br>
NSWI004 mailing list<br>
<a href="mailto:NSWI004@d3s.mff.cuni.cz" target="_blank" rel="noreferrer">NSWI004@d3s.mff.cuni.cz</a><br>
<a href="https://d3s.mff.cuni.cz/mailman/listinfo/nswi004" rel="noreferrer noreferrer" target="_blank">https://d3s.mff.cuni.cz/mailman/listinfo/nswi004</a><br>
</blockquote></div>
_______________________________________________<br>
NSWI004 mailing list<br>
<a href="mailto:NSWI004@d3s.mff.cuni.cz" target="_blank" rel="noreferrer">NSWI004@d3s.mff.cuni.cz</a><br>
<a href="https://d3s.mff.cuni.cz/mailman/listinfo/nswi004" rel="noreferrer noreferrer" target="_blank">https://d3s.mff.cuni.cz/mailman/listinfo/nswi004</a><br>
</blockquote></div>
_______________________________________________<br>
NSWI004 mailing list<br>
<a href="mailto:NSWI004@d3s.mff.cuni.cz" target="_blank" rel="noreferrer">NSWI004@d3s.mff.cuni.cz</a><br>
<a href="https://d3s.mff.cuni.cz/mailman/listinfo/nswi004" rel="noreferrer noreferrer" target="_blank">https://d3s.mff.cuni.cz/mailman/listinfo/nswi004</a><br>
</blockquote></div>