Tuesday, 13 November 2012

Midterm is coming SOON!

The project 1 had been a great practice of my programming skills. It took a while to get used to figuring out how to solve a problem on my own, but it greatly contributed to my learning experience. I would post some hints of what I think would be a great strategy to follow when experiencing difficult programming task:
1) Copy out a portion of code that has an error and look specifically into it. Spend some time figuring out exactly what it does and what is the purpose of it.
2)  Go through the relevant portions of textbook that have the topics covered from the problem code, search through DrRaket online help database for explanation and examples. Might provide you some hints.
3) The hardest step is to improvise! Change one relevant portion of the code at a time and click RUN to see what happens. If you do not know how to solve it, the only thing you really need is time. Keep your eye on the error messages and make sure you understand what is wrong and what needs to be fixed.
4) You may also want to look at the stepper. Which is a great tool to help you get to the right step where you messed up and find a specific spot that needs to be fixed.
5) If you are completely stuck, STARE at the code, at the problem that needs to be fixed and think what you can do fix it. Or do not think. The more time you spend on it the more likely it will come to you.
6) Never give up! Just remember that any problem that you've got can be solved. Maybe not now, but sometime soon it would be possible.

P.S. right when i submitted my project i noticed that when "down" key is pressed it stops the clock but also puts clock-hands into 1 2 3 mode. For a minute I panicked and thought that it should freeze at the time when I hit the "down" key. However when I checked the instructions it did not say anything about that, and I could not think of way how to do it. So if anyone else had the same thought in their mind please share if you had come up with some idea's on how to solve it! 

Friday, 2 November 2012

Project 1 goes on.

New evening brings up new programming issues. Now DrRacket force-closes every 10 minutes when I try to fix the function with several windows or tabs open. That is very frustrating and the worst thing is that there is nothing I can do about it. Too busy actually trying to make the clock work. What a tough problems! after first one with the colour problem, I was able to figure out it quite easily, now is turn for the im. And WOW they are so alike, but because its an image and not a colour I have to find what to add to make the definition complete. Going through the help and previous lectures without any progress, it is not easy to find the solution right away, but I have time to figure out by myself what is going on and make it work!

Thursday, 1 November 2012

Working on Project1

On Monday took a first glance on the project. At first it seemed to be an extremely difficult task, because there are so many things to work on and mistakes are all over the place. However when I took the courage and tried to actually start working on the first one it is not as bad as it looks like. To start with I took the part of the code that needs to be fixed and put it into separate tab in the DrRacket, so you would not be distracted with the code below and above the needed part. For the writing the check-expect function for a definition is quite an easy task, just explore the definition very carefully and figure out the idea behind it, than just repeat it so program would perform the test and if it is successful, than you are done!

Now it is time to tackle all the others!!!