Hi Tim,
Tim Bowden wrote:
I think some (of course, not all) universities would teach a language or
programming first by getting students to work alone. And then a year or
two later, put them into groups and then that's when the teachers go
nuts. :-)
I wonder if it's not time well spent to have students doing
git/svn/whatever right from the start (regardless of language)? Just to
get students used to the idea at a very simple level. After all, open
source or not, code repos are something everyone has to get used to at
some point.
I don't want to argue for/against how universities do things. I'm
nowhere near qualified and my comment was about what I've observed and
not what I support.
That said, you have a good point. In a 4-year degree, I believe some
places do the above in second-year; others do it in third-year. I think
first year has been avoided since (depending on the education system)
you might have students that are taking computer science as an elective
and really have no intention of going further. (I knew of classmates in
that situation.) If they leave the first year class and end up with a
basic notion of how to formulate an algorithm, I believe that would be
a "success".
I've also heard of repositories as a deterrent from cheating. If you
make a rule to commit every day, it leaves a record of how your project
[made by just you] grew. I'm not so sure how effective this is...
Ray
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
