• View
• Edit
• History
• Print

TrongsWImpMode

Trong's WImp Mode

Summary and Problems

When first starting the recreating of wimpmode, I thought that it was a simple task, but I was soon to be disappointed. It was a tedious task that required much attention to even the smallest of details such as the placing of code into the appropriate spot. I had made plenty of mistakes regarding the placing of code in the right places. At often times, I would become frustrated for long periods of time for the stupidest mistakes. One type of mistake was the wrong spelling. I would waste precious time to find out what my problem was and when I found out that it was a simple spelling error, I became mad at myself for not being able to see such an amatuer mistake. Another mistake that I made was that I often forgot to put semi-colons after a command. This would also waste much time in trying to figure out a mistake. But in the end, I am glad that I made those mistakes because I now carry a stronger knowledge of computer programming.

Lessons Learned

In this lab report for wimp-mode, I have learned many lessons that I did not know before that will help me in understanding computer programming better. For example, as simple as it may seem, I have learned that programming requires a lot of logic and planning for things to work. To start the lab, it is best to produce a flowchart before anything else because by making one, you can see the function layout and you would also have logic to go by. If a flowchart is not made, it would be much harder to come up with a code to imitate wimp-mode because you would also be trying to remember all of the parts of the function, which is a waste of time. You will not be able to have the luxury of seeing your plans on how to carry out this project. Instead of trying to come up of a code that imitates wimp-mode all at once, I learned that it is much more efficient to come up with a code by breaking down the function to pieces to understand the process better. Also by breaking it down, it makes it much easier in the end because the only thing left to do is to connect the pieces together to develop a mimic for wimp-mode. A final lesson I learned was to not have loops intersect another loop. This is important because it relates back to the flowchart concept I talked about earlier. If you have loops intersecting, chances are that you probably did not have a flowchart and you therefore don’t have a good logic to go by.

When I was going about making my code, I had a problem of using the correct logic. Instead of starting with a flowchart, I randomly started coding without any logic to go by and right away, I started incorrectly. Another flaw I had was that I did not use any debugging tools (explained more on next page). Without debugging tools, there was no way for me to know exactly where I was in my code. A final flaw that I saw hindering my code was when I was coding, I plugged in random commands until I reached to something that I wanted. I found out that this type of coding is one of the worst kinds because not only you don’t have logic, you also won’t learn much from this way of coding. Again, this can be solved by simply having a flowchart.

Trong Wimpmpde Picture Δ

Trong's Wimp Mode Code Δ

Trong's Wimp Mode Flowchart Δ

Back to Trong