25/May - End

Today i put my first version of my program into python. It had many bugs.

This was my first run after writing it out. After this i went back to my code and found that i had repeated one of my statements, on accident. I then removed the mistake and ran the program again.

This time i found a typo in my code. I now realize i am going to have a lot of these that i will have to proofread my code a lot.

Something good did come out of this test as i did get a chance to test my unexpected boundary cases, which seem to be in working order. Hooray!

I found what was causing the error and all it was, was a simple (x).

I then fixed this and tested my program again. The program seems to run! It has working inputs and tells the user if the guess is in the word or not but does not end once finishing the word. The program will need a lot of work still to be done on it but this is a great step for my assessment as i now know that my program kind of works.

==================================EDIT==================================

I tested my program with the word "hi" and found out that my program does end, it just doesn't recognize double letters in a word. I knew this was going to be a problem but I will find a way around this. The program also tells the user when they loose, which is great because it means it is working properly. If the user gets 12 guesses wrong it tells the user they loose and what the word was.

25/May - Start

This lesson i plan to put my algorithm v2 into python for a test. I realize it will have many bugs i will have to fix.

22/May - END

Today i decided to put all of my processes into separate modules so they can be called when needed. I found out how i can use an array and how to remove letters out of it. Next time i plan to produce version 2 of my pseudo code with modules and arrays.

22/May - Start

Today i found out that when my pseudo code tells the user to guess again nothing happens. It will print the instruction but nothing will happen afterwards. To fix this i will create a working function for my pseudo code to make sure that the user can guess again when they input an invalid guess. I plan to do this by putting my main working into a module to make sure that it can be called when needed.

14/May - End

Today i created my algorithm log, I finished specifying my variables and started to list my inputs and outputs.
I also decided to have a play again function in my algorithm. I will do this by putting my main process into a module and when the “play again” module is called it will ask the user if they want to play again, (y, n). If the user answers yes, the program will run the “Main” module. If no, the program will use the function inside python called “exit()” which will terminate the program. This will be included in version 2 of the algorithm which i plan to make soon.

14/May - Start

Today i plan to create an algorithm log so i can log my changes to my algorithm in one text document, but of course all my logs will be on my blog too, to prove that i did these changes when i said i did.

11 May - Home

I just finished reviewing my Managing achievement standard to make sure I had finished everything that it said on the marking schedule