First three weeks in CSC148

It has been about 3 weeks since I took CSC148 course. And I think it would give me a new impression of programming. In first three weeks, the course focused on the class, especially stacks, inheritance and recursion. And we have written the first assignment in this semester.

The first assignment is to design a two-player game named subtract square, and the general game state will be used through the term. I have learned a lot through this assignment.

First of all, the most important thing I learned is that the assignment requirement should be read carefully and every detail should be memorized or recorded. At first, my partners and I didn’t notice that five classes were needed, and we wrote the codes in one class, which was obviously not satisfied the requirement. After asking TAs, we had to rewrite the whole program. Further and more eventually, it is important to indicate what should be ran in every class, and docsting as well as comment must be clearly written. These comments would become essential clue. What’s more, order is important in python, especially ‘or’. If one statement is fail, computer will not evaluate remaining statements. Thus, the order of these ‘or’ statements should be written in the most suitablde order. Finally, debugging is vital. This can help us to find the mistakes we did not pay attention.

Overall, writing a perfect program should think over a lot things. It cannot be completed in few days without careful consideration.

WHY GEEKS SHOULD WRITE

              WHY GEEKS SHOULD WRITE

When talking about geeks, the image that occurs in our mind is always that a hacker sits in front of a computer with numerous lines of codes on the screen. What’s more, the hacker’s fingers move so quickly to type the keyboard and he seems to be dramatically skilled in programming. It seems that writing codes, testing them and debugging are the most important things that geeks work for a large amount of time. However, keeping writing a writing record for what they have done is also vital for them in their daily work. The reasons of doing this are as followings:

1)Recording their thought. It is really important for every computer scientists to write down their every ideas flashed in their mind. Some ideas might look ridiculous at the first time, but they may significantly contribute to the success at the end.

2)Writing down changes they made in the codes and reasons why they did that. Some changes they made would be not beneficial for their program. As a result, keeping a record may easily help them correct their wrong moves.

3)These records may become a worthy experience for the future. Furthermore, this experience would avoid geeks making the same mistakes.

4)Communication is also important for computer scientist. Communicating the ideas they had and the mistakes they made would be dramatically beneficial for each other.

5)Inspiration. Setting goals at the beginning of a mission would dramatically help geeks to keep on towards the objective.

Overall, geeks should not only write codes in the labs, but also write a lot to record their workings.