Unfortunately I have not been keeping up with my blog posts, but I'll make a post going over what I remember from working on Tetris with the entire class. So, the first step was to come up with a design within our teams and then have delegates collaborate and come up with a final design. My team, again, was very agreeable, but I didn't pay much mind to it, which looking back I should have. After the delegates came together on a final design, the class received a 'finalized' version of the design about an hour before the class that it was due, so I didn't really even know what it was. Then we spent that class re-factoring our designs.
That gets the design part up to speed, now our group's implementation. Our group really became a duo I feel like. The others in the group kind of fell off and disappeared. Communication went down with the others, one even stopped talking with us all together until about yesterday or the day before. The others, were very hesitant on talking, accepting tasks to work on, and became hard to work with to be honest, because the amount of help they needed to complete a task was excessive.
My work: Since the design was kind of flawed, since it didn't have much time to settle, I was under the impression that the FallingPiece was handling it's collisions, and it was told if there was a collision. Therefore, I wrote functions in falling piece to handle those collisions, or atleast simulate it so we could keep working forward. That was scrapped. Next, I "helped" write the Audio system. I say helped in quotations because the teammate that was in charge of it asked for a demo of how to do it, so I demo'd how to write it, just for playing the theme. Next, he asked for demos for the other functions, so I did it. At this point, I thought to myself I might as well just be in charge of it. I told him that, and it started some conflict in the group, but eventually I handed him over my demo, so he could 'use it as reference'. Once he had submitted it and said he was done, we advised him that it should be a singleton, which of course he needed help on. Next, when we tried implementing it, it didn't work; because since he was still following demo code I wrote, he didn't account for file locations, so I fixed that. Other than that, I helped Alejandro with his tasks of gluing the game together, since I had a sneaking suspicion that it was a lot for one person to handle.
P.S. Since this is the last post for the class, I'll be posting the rest of Peter's Laws if you've been keeping up.
#6 - When forced to compromise, ask for more.
#7 - If you can't beat them, join them, then beat them.
#8 - If it's worth doing, it's got to be done right now.
#9 - If you can't win, change the rules.
#10 - If you can't change the rules, then ignore them.
#11 - Perfection is not optional.
#12 - When faced without a challenge, make one.
#13 - "No" simply means begin again at one level higher.
#14 - Don't walk when you can run.
#15 - Bureaucracy is a challenge to be conquered with a righteous attitude, a tolerance for stupidity, and a bulldozer when necessary.
#16 - When in doubt: THINK!
#17 - Patience is a virtue, but persistence to the point of success is a blessing.
#18 - The squeaky wheel gets replaced.
#19 - The faster you move, the slower time passes, the longer you live.
No comments:
Post a Comment