I couldn't post this yesterday because my internet was disconnected, so here is my weekly report now.
On Monday, we continued working on our project, the SIN number validation project. I almost finished working on it, but I didn't finish it completely with all the details. I found the project pretty hard, becuase it was a pretty long project and I messed up a couple of times.
On Tuesday, we continued working on our SIN number validation. I finished the program, and i almost finished the documenting part of the program, but i still needed to do some finishing touches. I ran out of time, so i plan on finishing the documentation up on the next day.
On Wednesday, I finished documenting my SIN number validation program, and it was ready to be marked. I was one of the first ones in that day to be marked. I thought i did a pretty decent job on the program, because it was doing everything it was supposed to be doing. One flaw was that i forgot to change the name of the program from Form1 to SIN Validation or something like that. The teacher said that other than that i did pretty well.
On Thursday, the class was still being marked of their projects. We also had a little lesson on drawing on Visual Basics, which was pretty interesting. Next, for those of us who had gotten their projects marked, we were to work on some exercises involving drawing in VB. I got some of the exercises done, but because this wasn't a part of the curriculum, we didn't have to finish it.
On Friday, the class finshed getting their projects marked. Also, we got our tests back, the ones we took some time last week. I did really well. I got a 93%! We also worked on a program which uses Test results and does something with it. I got started on it, but I found it hard because I didn't know where to start from.
Some difficulties I faced this week is that I didn't know how to write some parts from the SIN validation project, so my friend and I worked together to figure out some parts that we didn't get. Also, I didn't understand at first how to draw in Visual Basics, but as we moved along, i started to understand it more and more.
Friday, May 4, 2007
Friday, April 27, 2007
TIK weekly report
On Monday, we learned something new called the timer control. That is a device in Visual Basics which enables you to create things like a stopwatch, or a clock program. We also got some practise by creating our own clocks and creating stopwatches in Visual Basics. Some of the difficulties i faced that day was that i didn't understand fully how to create a stopwatch, so i asked people for help.
On Tuesday, it was a half day, so we didn't start anything new. But, people presented their projects about types of computer related jobs and occupations. I didn't present because i wasn't here for the project. Also, since it was a group project, I couldn't to it later on either.
On Wednesday, we had a review period because we were to have a test the next day. The teacher gave us the whole period to study and review what we have learned for the test. The teacher also gave us a review sheet for us to work on, so we know what to expect on the test. Some difficulties i faced this day was that some of the things were from a long time ago, so i had to look it up on my notes or ask other people for the answers or the notes that i might have not had.
On Thursday, we had out TIK test. Maybe it was because i studied alot the other night, or maybe it was just the test itself, but the test seemed very easy for me. Except for some questions that i forgot how to do completely, i answered almost all of them with detailed explanation and everything.
I wasn't in TIK on Friday because i had to leave school for a personal reason.
On Tuesday, it was a half day, so we didn't start anything new. But, people presented their projects about types of computer related jobs and occupations. I didn't present because i wasn't here for the project. Also, since it was a group project, I couldn't to it later on either.
On Wednesday, we had a review period because we were to have a test the next day. The teacher gave us the whole period to study and review what we have learned for the test. The teacher also gave us a review sheet for us to work on, so we know what to expect on the test. Some difficulties i faced this day was that some of the things were from a long time ago, so i had to look it up on my notes or ask other people for the answers or the notes that i might have not had.
On Thursday, we had out TIK test. Maybe it was because i studied alot the other night, or maybe it was just the test itself, but the test seemed very easy for me. Except for some questions that i forgot how to do completely, i answered almost all of them with detailed explanation and everything.
I wasn't in TIK on Friday because i had to leave school for a personal reason.
Friday, April 13, 2007
TIK weekly report 9
This week in TIK, we did many things, which were finishing up our pizza order programs, start learning how to create loop programs (For...Next), and we also learned a way to trace our programs, to make us understand better the concept of loop programming.
Because it was a 4 day week this week, we didn't have any class on Monday. On Tuesday, we continued working and finishing off out pizza palace order form program which was our midterm project. We finished it and we also had time for the teacher to mark our program. Overall, I think we did pretty well, but there were some places that we made easy mistakes that could have been prevented if we checked more throughly. I didn't face any problems that day, because we were practically done our program and all we had to do was finish it off.
On Wednesday, everyone finished their programs and we started on how to create loops in Visual Basics. We learned how to create loops with the For and Next statements. It seemed pretty easy, because all we had to do was copy what was on the sheet as an exercise. I didn't finish the whole thing that day. Some difficulties I faced that day was that I didn't understand how to start the whole loop program, so I got some help from other people.
On Thursday, we had a lesson on how to trace programs in Visual Basics. Basically, we were taught how to make it so that we know exactly what process the programs we create goes through before the final statement shows up on the screen. We got a handout to work on, which was very easy, because all we had to do was copy exactly what the handout said and then copy what the answer showed up as. I didn't face any problems that day.
On Friday, we continued our work on loops with the For and Next statement, and we also continued working on tracing the programs we created. But this time, the programs were a bit more complicated and we had to explain what was happening in the program in words. Some of the difficulties I faced that day was that I didn't know that you were supposed to write down the information every time a variable changes, but I didn't know that, so my information table got really long. Also, I didn't completely understand how to explain the program in words, so I asked others for help.
Because it was a 4 day week this week, we didn't have any class on Monday. On Tuesday, we continued working and finishing off out pizza palace order form program which was our midterm project. We finished it and we also had time for the teacher to mark our program. Overall, I think we did pretty well, but there were some places that we made easy mistakes that could have been prevented if we checked more throughly. I didn't face any problems that day, because we were practically done our program and all we had to do was finish it off.
On Wednesday, everyone finished their programs and we started on how to create loops in Visual Basics. We learned how to create loops with the For and Next statements. It seemed pretty easy, because all we had to do was copy what was on the sheet as an exercise. I didn't finish the whole thing that day. Some difficulties I faced that day was that I didn't understand how to start the whole loop program, so I got some help from other people.
On Thursday, we had a lesson on how to trace programs in Visual Basics. Basically, we were taught how to make it so that we know exactly what process the programs we create goes through before the final statement shows up on the screen. We got a handout to work on, which was very easy, because all we had to do was copy exactly what the handout said and then copy what the answer showed up as. I didn't face any problems that day.
On Friday, we continued our work on loops with the For and Next statement, and we also continued working on tracing the programs we created. But this time, the programs were a bit more complicated and we had to explain what was happening in the program in words. Some of the difficulties I faced that day was that I didn't know that you were supposed to write down the information every time a variable changes, but I didn't know that, so my information table got really long. Also, I didn't completely understand how to explain the program in words, so I asked others for help.
Wednesday, April 4, 2007
TIK weekly report 8
This week in TIK, we didnt do much because it was a 4 day week. Also, it was especially short for me because i was sick on Monday so it was only a 3 day week for me. Because i wasn't here on Monday, i dont know exactly what the rest of the class did, but i heard from a friend that they got partnered up to work on a major projet that we have to hand in by the end of this week.
On Tuesday, when i came back, my partner already made the program layout, so we had to start writing the program itself. what we had to create was a pizza order menu sort of thing, and in the end it had to show the total cost of the pizza and other things you might order with the pizza. we had the whole period to work on that. Some things that were difficult for me was that because the program itself was very big, i didn't know where to start. i solved that problem by asking people and the teacher for help.
On Wednesday, we continued working on our projects. We got alot of things done today, like finish up writing the program itself. Now all we have to do is write the program for the options at the top, for example, changing the price of a certain item. Some problems i faced that day was that our program kept showing unnecessary decimals, so we had to figure out what was wroning with it and how to fix it. we figured it out by asking people.
On Thursday, we continued working on our pizza order programs we started on the dialog boxes today, because I finished up on the order program. I had to create three dialog boxes, and I finished working on the first one and the second one, but I didn't finish the third one. I plan on finishing up the third dialog box and documenting it on Tuesday.
On Tuesday, when i came back, my partner already made the program layout, so we had to start writing the program itself. what we had to create was a pizza order menu sort of thing, and in the end it had to show the total cost of the pizza and other things you might order with the pizza. we had the whole period to work on that. Some things that were difficult for me was that because the program itself was very big, i didn't know where to start. i solved that problem by asking people and the teacher for help.
On Wednesday, we continued working on our projects. We got alot of things done today, like finish up writing the program itself. Now all we have to do is write the program for the options at the top, for example, changing the price of a certain item. Some problems i faced that day was that our program kept showing unnecessary decimals, so we had to figure out what was wroning with it and how to fix it. we figured it out by asking people.
On Thursday, we continued working on our pizza order programs we started on the dialog boxes today, because I finished up on the order program. I had to create three dialog boxes, and I finished working on the first one and the second one, but I didn't finish the third one. I plan on finishing up the third dialog box and documenting it on Tuesday.
Friday, March 30, 2007
TIK weekly Report 7
This week in TIK, we learned how to add menus and dialog boxes to our program, so that the user has more choice and can choose what they want to calculate.
On Monday, we recieved a project called a payroll application, and we had to work on it. What payroll application is is that we just basically had to make a program that shows how much the user makes if they sell a certain number of Coffee at a coffee store. I couldn't start on that yet, because I didn't finish a program from the other week.
On Tuesday, I finally started on the payroll application, and I finished creating the basic outline of the program and how it was going to look like. Then, I started working on the writing part of the program.
On Wednesday, we continued working on our payroll applications and I basically got the whole thing done. It took everyone a while to finish, because the program had to do alot of functions, and we had to write every single one of them.
On Thursday, we got a sheet to extend our payroll application to make it do more than just give how much the employer made. We had to now create menus and dialog boxes to our program, so that you can change how much the employer makes per hour.
On Friday, we had a lesson on how to make menus and dialog boxes to our program, because the teacher told us something was wrong with the instruction sheet that she gave us the other day. After, we had some time to work on our own programs, and I nearly finished creating the menus and dialog boxes on my program.
Some difficulties that I faced this week is that because I didn't finish a program from last week, I started about half a class later than most people, so I was a bit behind schedule. Also, because the payroll application was a very long program to write, I got mixed up or lost while writing the program. I also didn't understand fully how to create menus and dialog boxes, so I had trouble moving on. I solved all those problems by asking people for help whenever I needed their help.
On Monday, we recieved a project called a payroll application, and we had to work on it. What payroll application is is that we just basically had to make a program that shows how much the user makes if they sell a certain number of Coffee at a coffee store. I couldn't start on that yet, because I didn't finish a program from the other week.
On Tuesday, I finally started on the payroll application, and I finished creating the basic outline of the program and how it was going to look like. Then, I started working on the writing part of the program.
On Wednesday, we continued working on our payroll applications and I basically got the whole thing done. It took everyone a while to finish, because the program had to do alot of functions, and we had to write every single one of them.
On Thursday, we got a sheet to extend our payroll application to make it do more than just give how much the employer made. We had to now create menus and dialog boxes to our program, so that you can change how much the employer makes per hour.
On Friday, we had a lesson on how to make menus and dialog boxes to our program, because the teacher told us something was wrong with the instruction sheet that she gave us the other day. After, we had some time to work on our own programs, and I nearly finished creating the menus and dialog boxes on my program.
Some difficulties that I faced this week is that because I didn't finish a program from last week, I started about half a class later than most people, so I was a bit behind schedule. Also, because the payroll application was a very long program to write, I got mixed up or lost while writing the program. I also didn't understand fully how to create menus and dialog boxes, so I had trouble moving on. I solved all those problems by asking people for help whenever I needed their help.
Wednesday, March 21, 2007
TIK weekly report 6
On Monday, we had a lesson on types of data, or "datatypes". Datatypes are things you write to show what symbol or word represents the variable. For example, integer, single, string, etc... We also started working on a new program, in which we have to make a scroll bar go leftwards if the temperature is cold, and rightwards if the temperature is warm. it also converts the fahrenheit to a celsius. Some problems I had encountered that day was that I didn't first fully understand what we had to make our program do, so I had a bit of a trouble. I solved my problem by asking others for help.
On Tuesday, we continued working on our visual basics programs. I finished the program almost half way through our class, so I started working on the Practise Excercise we had to do after we were finished with our first programs. We basically had to add a bar, and makes it so that when we move the bar, the temperature rises and then does the same thing with the second bar as it did with the first program. I didn't encounter any problems that day.
On Wednesday, our teacher wasn't here so, we worked on a different, writing assignment. We had to read a sheet called the Internt Safety Pledge, and I personally think that the Internet Safety Pledge is useless, and is not necessary, because no child, in their right mind, would follow the Internet Safety Pledge. We had to write a minimum of 3 paragraphs response on what we know about internet safety. Some difficulties i encountered that day is that I didn't know what to write about at first, but I got the ideas and finished the work on time.
On Thursday, we got a package with a bunch of types of string that we had to write out what each of them did, so it took the whole period. After that, we started working on a program that does at least 10 of those functions. Some problems I encountered that day was that I didn't understand how to set up the program, so it was hard for me to start. I solved the problem by asking people for help
On Friday, we continued working on those programs. At first, I finished setting up the program so that I can start writing it, but it was hard because I didn't know what to do. In the end, I figured out how to write the program, but because it was so late, I couldn't finish the program completely.
On Tuesday, we continued working on our visual basics programs. I finished the program almost half way through our class, so I started working on the Practise Excercise we had to do after we were finished with our first programs. We basically had to add a bar, and makes it so that when we move the bar, the temperature rises and then does the same thing with the second bar as it did with the first program. I didn't encounter any problems that day.
On Wednesday, our teacher wasn't here so, we worked on a different, writing assignment. We had to read a sheet called the Internt Safety Pledge, and I personally think that the Internet Safety Pledge is useless, and is not necessary, because no child, in their right mind, would follow the Internet Safety Pledge. We had to write a minimum of 3 paragraphs response on what we know about internet safety. Some difficulties i encountered that day is that I didn't know what to write about at first, but I got the ideas and finished the work on time.
On Thursday, we got a package with a bunch of types of string that we had to write out what each of them did, so it took the whole period. After that, we started working on a program that does at least 10 of those functions. Some problems I encountered that day was that I didn't understand how to set up the program, so it was hard for me to start. I solved the problem by asking people for help
On Friday, we continued working on those programs. At first, I finished setting up the program so that I can start writing it, but it was hard because I didn't know what to do. In the end, I figured out how to write the program, but because it was so late, I couldn't finish the program completely.
Thursday, March 8, 2007
TIK weekly report 5
this week in TIK, we had learned quite a few new things about visual basics. We learned about Case programming, and we also learned about debugging. at first, i found the case program more complicated than Elseif programming, but as i got used to it, it was more convenient. On debugging, we learned about 3 types of errors:
logic error, complier error, and run-time error. We also somewhat learned how to fix those three errors. now that we know what these errors mean, that means that i can debug my program if there are any errors without problem. On wednesday, i started on the second question of my case programming, because we had to hand it in by the end of friday. by the end of the day, i had gotten about half finished. on thursday, i finished the question Case off and put it on my usb key. before that, i made sure that i finished it properly, and that the program was working, and ready to be marked. we also had a quiz that day. i thought it was pretty easy. I forgot how to do some parts, but all in all, i think that i passed. on friday, it was the day before march break, so not alot of people came to class. i started and finished my flowchart for the question we had to hand in.
Difficulies:
some of the difficulties i faced during this week is that:
- i didnt fully understand how the Case programming worked, so i asked a couple of people and then they helped me understand better
- i didnt understand what debugging meant as in when the program stopped and told me what was wrong, i had trouble understanding it, so i asked people for help, and they helped me fix the problem, and helped me on figureing out how to do it by myself.
logic error, complier error, and run-time error. We also somewhat learned how to fix those three errors. now that we know what these errors mean, that means that i can debug my program if there are any errors without problem. On wednesday, i started on the second question of my case programming, because we had to hand it in by the end of friday. by the end of the day, i had gotten about half finished. on thursday, i finished the question Case off and put it on my usb key. before that, i made sure that i finished it properly, and that the program was working, and ready to be marked. we also had a quiz that day. i thought it was pretty easy. I forgot how to do some parts, but all in all, i think that i passed. on friday, it was the day before march break, so not alot of people came to class. i started and finished my flowchart for the question we had to hand in.
Difficulies:
some of the difficulties i faced during this week is that:
- i didnt fully understand how the Case programming worked, so i asked a couple of people and then they helped me understand better
- i didnt understand what debugging meant as in when the program stopped and told me what was wrong, i had trouble understanding it, so i asked people for help, and they helped me fix the problem, and helped me on figureing out how to do it by myself.
Subscribe to:
Posts (Atom)
