On May 10, 2017, at 6:40 PM, David Mason <dma...@ryerson.ca> wrote:
>
> On 10 May 2017 at 17:05, Artur Shepilko <nomadb...@gmail.com> wrote:
> Not sure about the objectives the students are learning in this
> course, but if it in any way relates to programming, recognizing as
> to what to keep under version control is a reasonable objective on its
> own.
[snip]
> ...covers 4 very different programming languages in 12 weeks. There is no
> time for nuance in SCM details.
Do you not mark down homework for bad code formatting, poor variable names,
missed corner cases, poor commenting, etc.?
I don’t see “lazy checkins” as any different.
And mark them down for poor-quality checkin comments while you’re at it.
Yes, this means lots of ways to mark down, so that no student is expected to
score 100%. That problem also has a solution: curve grading. I once took a
class where the students achieving an “A” grade might get 2/3 the answers on a
test right.
> ...making SCMs and TDD intuitive concepts for all humans...
"The only intuitive interface is the nipple. Everything else is learned.”
— Bruce Tognazzini
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
