Go back to: General discussion
Hey guys, opening this thread to discuss about work and peer review. These are my initial thoughts that, as with everything else, can be changed through your input and feedback.
Assignments: I don't really want to use the word 'assignment' cause it sounds like I will be giving you guys fixed tasks that you have to resolve. The only thing I would like to ask is that we all keep up with the reading for the week (see syllabus), and from there we can start working on whatever our interests takes us. We could tackle the first couple of ideas as a group, and then fork into smaller groups or individual projects. That is all open right now.
I would like to pair with all of you guys, at least once, during the course (pair as in pair programming).
I would also like to ask you guys to blog about what is going on in the course, at least once a week. The posts can be about development, documentation, your own thoughts about the architecture or the design, a piece of code you've written, and so on.
If you guys can think of a word that fits better than 'assignments' we can start using it.
Peer review: My initial idea is that at least 2 people in the group will review somebody else's work for the week (whatever you decide to publish for the week, be it code, reflection thoughts, etc.), and give feedback. We can create some kind of roster for this. So our work will be reviewed by at least 2 others, and we will have to review at least 2 other people (but not limiting it to 2).
As a final note, I just want to reitarate that we are all adults, we all have full-time jobs, families, and so on, so please don't expect me chasing after people to get stuff done. As in any p2p group, you are responsible for your own learning.
Look forward to hearing your ideas!
Jos
Course Work and Peer Review
Hey guys, opening this thread to discuss about work and peer review. These are my initial thoughts that, as with everything else, can be changed through your input and feedback.
Assignments: I don't really want to use the word 'assignment' cause it sounds like I will be giving you guys fixed tasks that you have to resolve. The only thing I would like to ask is that we all keep up with the reading for the week (see syllabus), and from there we can start working on whatever our interests takes us. We could tackle the first couple of ideas as a group, and then fork into smaller groups or individual projects. That is all open right now.
I would like to pair with all of you guys, at least once, during the course (pair as in pair programming).
I would also like to ask you guys to blog about what is going on in the course, at least once a week. The posts can be about development, documentation, your own thoughts about the architecture or the design, a piece of code you've written, and so on.
If you guys can think of a word that fits better than 'assignments' we can start using it.
Peer review: My initial idea is that at least 2 people in the group will review somebody else's work for the week (whatever you decide to publish for the week, be it code, reflection thoughts, etc.), and give feedback. We can create some kind of roster for this. So our work will be reviewed by at least 2 others, and we will have to review at least 2 other people (but not limiting it to 2).
As a final note, I just want to reitarate that we are all adults, we all have full-time jobs, families, and so on, so please don't expect me chasing after people to get stuff done. As in any p2p group, you are responsible for your own learning.
Look forward to hearing your ideas!
Jos