Friday, September 13, 2013

week 3


First of all, I want to talk about three quizzes in this week. My performances are stable in these three that I could answer most of the questions correctly. However, each time I would have one question wrong. For example, considering the context of collatz, what does n + (n/2) + 1 mean? It may be a little tricky. If I had more time, I think I could solve it. Yes, that is what I want to say. Quiz time is too short to me. From another perspective, I need to react more quickly.

I am still keeping a confusing attitude for the teaching content in class. We have had three weeks’ lectures. What we learnt is not well organized. Yes, we knew assertions and exceptions and we also knew iostream. But shouldn’t we start to learn from Chapter 1 in the textbook? Maybe we should start with what is object and what is object-oriented programming? Then we should talk about how to define a class and what are properties of a class? It I were the professor, this could be my choice. However, I believe the professor has his idea and his teaching experience would ensure that his style has better effect for us. Just listen carefully.

Last but not least, I really appreciate what the professor in Friday’s lecture about pair programming. It really helped me to learn a lot. To be honest, in the past I am a student who is hesitate or even hates to collaborate with other student for projects. It is mainly due to some unsuccessful project experience. I met a lazy and irresponsible teammate who didn’t do his job well. I was very angry with that and spend too much time on it, nearly completing the whole project myself. From then on, I lost confidence of finding a good teammate. Now I think what I did was wrong. I shall have a communication with teammates when I think we need a talk. It would probably solve the problem. As the professor said, most of current software are developed by a team, not an individual. Communication skill is especially important when we hunt for a summer intern or full-time job in the future.

No comments:

Post a Comment