Last week we had our first CSC148 term test, because I understood all the course materials, and I put everything that I could possibly put on the Aid sheet, the term test last wednesday was easy, it was a conclusion of everything we have learned so far. However, I spend too much time on question one, I wanted to make the content look good, so when I think my writing is messy, I erase it and rewrite it again, but we only had 50 minutes of test time. So as you can time, I didn't finish the term test at last, it was a really depressed feeling because I knew how to do all the questions but couldn't finish writing it. There was four questions in total that we have to write, I left half of the question blank, the final mark I got was 21/25, only if I finished the test paper. I have to learn the lesson and do the test efficiently.
Right after the term test we went back for one more hour of lectures, we learned the new concept about trees, and more recursion. It was confusing when I think of the concept of recursion last week, but after the lab, and more practice, I can feel that I'm more comfortable with the idea now. Recursion is like solving a large problem in the simplest way possible, we don't have to write more code for it, because the function will call itself. All I need is practices, more practices on coding will make my skills so much better!
Sunday, March 1, 2015
Wednesday, February 25, 2015
Week 4: Recursion
Recursion is a brand new idea to me. I have learned a bit of Java before the course CSC108 and CSC148. the strategy to implement Recursion code itself is not hard, it is the concept it is hard to understand. You write a function, and call the function inside the function itself. It could be infinite depth, depends on the argument you put in. It is challenging because we human don't usually understand things like that, when we do something, we think about what happens next, not what happens inside the things that just happened. It is a efficient way, but also abstract.
However, I found out that recursion can be related to a very famous movie: Inception. The movie is about a thief with that steals secrets from people's dreams. But somehow he got trapped in his own dream, that is a dream inside a dream, which is very dangerous, cause you could be trapped in there forever, and there can always be another level of dream inside that dream. Can you see the similarity between the movie and recursion? Yes, it could be so deep that you can't even imagine.
Coding is interesting.
However, I found out that recursion can be related to a very famous movie: Inception. The movie is about a thief with that steals secrets from people's dreams. But somehow he got trapped in his own dream, that is a dream inside a dream, which is very dangerous, cause you could be trapped in there forever, and there can always be another level of dream inside that dream. Can you see the similarity between the movie and recursion? Yes, it could be so deep that you can't even imagine.
Coding is interesting.
Thursday, January 22, 2015
Week 3: Why geeks should write
Geeks should write because writting in general can improve one's presentations skills and communications skills.Just because geeks usually does technical jobs doesn't mean that geeks won't face the problems where they have to talk to an client, discuss about the business and selling your ideas and product, where communication skills will come handy. If you have a very good product and excellent skills but poor at selling yourself and express your ideas, probably someone who has a worse skill than you will get the position you've always wanted.
Geeks should also write because writting things done is a good way to conclude your past work and setting up new goals. Knowing what mistakes you have made in the past and what to do to improve it, your own performance. Even if you didn't do so well in the past or had faliures, writting can help you rethink and going through the problems, and by going through the problems again you might find a solution to it!
Geeks should also write because writting things done is a good way to conclude your past work and setting up new goals. Knowing what mistakes you have made in the past and what to do to improve it, your own performance. Even if you didn't do so well in the past or had faliures, writting can help you rethink and going through the problems, and by going through the problems again you might find a solution to it!
Subscribe to:
Posts (Atom)