Priorities - A: high, B: medium, C: low; Status - _: unfinished, X: finished, C: cancelled, P: pending, o: in progress, >: delegated. Covey quadrants - Q1 & Q3: urgent, Q1 & Q2: important
C1XFind and contemplate Renato Constantino's "Veneration Without Understanding" (E-Mail from Federico Sevilla III)

1. Irony : 17:21

Categories: None -- Permalink
The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. — seen on the net

2. CS215 evaluation : 21:42

Categories: None -- Permalink

The modules were clearly explained and the engaging story helped motivate the students to work on the project. The students appear to have greatly enjoyed the exercise, particularly the creative background story that provided the context for their work. By reviewing other people's code, the students learned more efficient ways of performing the given task. They also became familiar with other modules in the system, allowing them to help each other to a greater extent during the implementation of their game project.

Suggestions for improvement:

Peer review of modules for identical tasks made it easy for students to copy and paste code they did not understand. Due to cases of plagiarism exposed during the project defense, stronger reminders about academic honesty are advised. Acceptable and unacceptable behavior should be defined. Alternatively, the assigned challenges could be similar enough for the common patterns to emerge but yet different enough to engage each student and make that student an "expert" on a topic his or her classmates did not fully tackle. Overall, working on multiple modules gave students a better appreciation of the different parts of a graphics engine and helped them learn how to write cleaner and more efficient programs.

3. CS215 evaluations : 22:18

Categories: None -- Permalink
Describe the way you reviewed another group's program. How much time did it take you? What did you learn? What did you help them learn?

- We were only able [...] our groupmates program because of lack of time and it's hard to connect to the net. - Not terribly long (I kind of skimmed thru the code). A lot of new concepts. Gave them game suggestions. - We evaluated their work at 10 PM, e-mailed them evaluation; worked on the submitted work for 59 seconds; dunno if they learned anything, though - We read thru their design, compiled and executed - First, I played the game. Then I described the game. It took me about 30 minutes. I learned new concepts from the game we reviewed but I don't know if they learned anything from us. - We just played their game and looked at their code briefly. Several minutes. We learned there is a timer task, we also learned about JFrames and menubars. Write readable code? =) - It took only about 10-15 mins. It was fun pero sometimes took our attention away from making the main game. - It took me just a little time to review another group's program. I got techniques and I learned more in them than if I had read books. - 10 mins / depends. Conceptualizing, threads. - I would usually download other people's program and see how they solved the problem. I would have to go over it a couple of times before learning it. - I wasn't able to really able to review-review, so I didn't really spend as much time. Although I learned reviewing our program. - I just sat down, looked at their comments and replied. 30 min? an hour? daily. Learnt (will learn) threading and animation. What did I help them learn? Not sure. They played a trick! And here I was, worrying about them before that, too... - Well, I tried to see what they have accomplished so far and the things they're having difficulty with. I tried reading about their description of their problem and suggested ways to go ahead, NOT SOLVE, the problem. - Around 10 minutes. We actually never got to review their code (and they never got to review ours too. we kind of started working really late... sorry) I think the reviews we made did not really help them at all. - Reviewing other people's programs helped me a lot. I learned so much from them. It takes a while to understand them fully however it was fun doing so. - Not much... 30 mins... I learned that I can critique and take time out to find errors. learned to be patient. - I'm not sure about this part... I thought of it as a waste of time =(

What do you like about reviewing?

- In our one and only review done, we were able to see that the other group is experiencing the same problems. - I learn and I teach at the same time. - It's fun - learning - It made me feel like i'm a game analyst or something. - We get to see the others' code and game. - Fun to look at what other people can do. - I get to use their program as well. - Seeing their program - I get to practice and learn how to do other programming techniques. - Uh... - Interactive. Say/read interesting things. - Everything: seeing progress, suggesting, commenting - N/A (Didn't review much.) - I learn and discover new things. - You get to test your knowledge in java and your creativity. - Having a pause from thinking what next to do in our game...

What do you think can be improved?

- Maybe instead of net, maybe group reviews can be done in class by alloting around 5-10 mins. It's really hard to connect to the net. - Nothing much. - It's fine the way it is - more things to review - Maybe I could have looked at their code and comment on that as well even if I don't understand it. - I have no idea. - Better matching up of reviewers/reviewees. - (no answer) - (...) more projects... - It would help to have more lectures. - Additional CS21A classes for those NOT really in CS or MIS - nice CS21A/b for those taking it as an elective. We're not really going to pursue programming per se so there =) - More time! Sometimes I don't get home until 5. And once, got home at 5:45. Scary. - none! (or more; not sure about handwriting) - I think we have to be required to include as early as possible. - (no answer) - Strict implementation of deadline. - ... removing the deadlines?! =) So that we don't panic if ever we won't make it to the deadline.

Did the review help you find errors or possible improvements that you would have otherwise overlooked or have had a hard time with?

- Yup. =) - Yes. - Yes - Yes - Um, yes! - No. - Not much =) - Yes, it did. The review made me want to improve. - =) - Yes. The review helped a lot. - huh... - Helped me think of improvements =). They had many ideas, but unfortunately I was only able to implement some - - Yes, suggestions are very helpful because you get to know what your program could have to improve. - We were never actually really reviewed... Only game plan comments were given. - Yes. - " - ...

What was the most helpful thing you learned from the reviews?

- They gave us suggestions on how to improve our games. - Double buffering. - How to use threads; canvas, double-buffering - Coding conventions - That we could finish the game (moral support) - We didn't submit specific progress reports. =) - Hm... to keep our code cleaner / coding conventions - Don't think what you want your program to be, think what your program's users will want it to be. - =) - I learned how to do other cool things! - I learned about arrays! and other stuffs for programming that I really didn't know about - The counter thing. Gave me the idea on how to separate the two counters. - =) - To be more creative... - I think debugging for errors was the most important so that I won't commit them again next time or in my own program. - We got no reviews! - encouraging each other is important! =)

How else did the review affect your design and programming?

- They help us make our program easier to make. - It helped us chug along. - We basically ripped off their suggestions - A lot... I have improved a lot - No idea - Same as above. - Use better variables - It made me research on other keywords. - =) - (no answer) - hmm... - Made me concentrate more on convenience methods. Because they had a suggestion of making more than the original 6 job classes, we became more determined to make layouting/adding sleeker. - ^_^ - N/A - It improved my programming because I got to talk with people and learn from them. - (no answer) - (no answer)

Compare the value you receive from the reviews with the additional work involved in reviewing other people's code. Do you think future students of CS21A should use peer review for all projects? more projects? fewer projects? no projects?

- All projects. - More, but not all projects. (Some projects that are too short should be exempt) - No comment - Yes - Yes Umm... nope, nope, nope... same # of projects. - I don't know =( - Peer review is OK - I think they should peer review only on major projects because it takes time - More projects! More time! =) - Reviews help a lot and I think the amount of projs for the sem is just right. - Yes I think reviews work, it's just us juniors didn't have the time to... - More projects. Not all projects, but I think it's useful for major projects. Although... maybe there could be some days when you could go without a progress report or review? So you can concentrate purely on the project. One problem I had though is that I focused so much on doing something in time for the daily progres that after 6:00, I'd stop work on the project to do other things. Kasi minsan, parang interruption yung progress report kasi I had to stop working on the actual project an hour early. - PEER REVIEW for all projects... - I think actual discussions would be more helpful... - I think they should use peer reviews more but fewer but challenging projects. - (no answer) - (no answer)

Would you like to have more peer reviewed projects in CS21B?

- Yes. But instead of net connections, can we just do it personally. - It's OK. I can live with or without it. - Not really - Yes - Yes. - Anything will do. - Well, one or less *hehe* - Yes - =) - Yes! - I guess it would be very helpful - Okay lang in moderation. - Yes, very much. It let's you know - I plan to procrastinate less, so yes... - Yes. - Yes, I hope we'll get reviews this time. - hmm... maybe more defense, buggy challenges, and donuts! =)