$msg = ""; $myaddress = "sacha" + "@" + "sachachua.com"; $page = "2003.10.16.php"; $page_title = "2003.10.16"; $page_updated = "2004-11-2106:44:1306:44:13-0500"; $maintainer = "sacha" + "@" + "sachachua.com"; require_once "include/calendar.php"; require_once "include/planner-include.php"; require_once "include/header.inc.php"; ?>
|10:00||10:30||Andaya, dela Torre, Esguerra, Irigo|
|10:30||11:00||Cruz, San Diego, Uynicky, Velasco|
|11:30||12:00||Aquilino, Arguelles, Corpuz, Uy|
Bonus, so they went to the J2sdk demos and the audio files and looked for au files. Followed the book. (Lori) Learned from friends how to display images.
Trying to slow down the ball's movement so that you can see the position.
How can you improve on your current game?
Making the ball move slower so that you can see how it goes. More reading the book or asking help from teachers and friends.
Let's take a look at parts of your code to see how you can improve it. Please open GCanvas. Can you try using a loop to simplify the constructor?
Clarissa applied a for loop to simplify her constructor code.
Can you try using variables to simplify the paint method?
Lori just added a for loop without real effect. Not so clear on programming. She hasn't developed a lot of debugging skills yet, and seems to perform changes by rote. Clarissa can find errors quiclky
Okay, she fixed that error. Minor simplification, but there's still something else that can me improved.
Lori's not too confident about programming yet, and she tends to make small, random changes in order to try to get a program to work. Clarissa is helpful.
Lori eventually got it. Yay!
It takes them a short while to brainstorm different ways to deal with a problem. Clarissa usually takes the lead
Then I asked them to define a class for the Player.
They identified x and y right away, and then Clarissa identified name after scrolling through the source code, and then Lori did so as well.
They aren't too familiar with arrays of objects yet. They know how to use search-and-replace, though.
They look like they're using arrays for the sake of using arrays, and this makes their program suffer in terms of readability. There's a lot of duplication of code.
Next step: Simplify code Learn about threading
Java for implementation + eliminated the smaller classes, merged them + coordination of work + conflict checking - no updated documentation - big OOP classes, but recognized it. + constant communication + prioritization + dealt with a setback - loss of a teammate
dependend on cliff's notes test data needs to improve on the OOP principles can recognize when code gets too big mostly structured, some methods adapted original design, hard to think about hanapan ng errors scheduling for the problem fixing, not too good underestimate + recognized dependencies based on the design and planned around that
mahirap pala yung print pair debugging
Essential use cases finished, but features/nice-to-haves not really