Apprentice Los Angeles game

McDonalds Video Game game

ill scarlett

nothig special

Weekly Status Report #17 (May 28 - June 1)

This week we we continued to learn about ergonomics and networking. We also had our test about those subjects on friday. Our project this week was our final project for the whole course. This project was to be done in groups. After we got our groups, we split up the work so that everyone was doing two challenges and it all added up to 100 points. I am working with Estatic E and Kool K. I think this group will be very productive and our outcome will be magnificent.

This week, I only had one problem and it was with the test situation. Before the test, I was having a panic attack so I was going crazy. Before I started the test, I didn't know what was going to be on it and I was really worried that I would fail. Now that it is done, I hope that I did good on it.

In the future, I hope that I will get more familiar with the terms in ergonomics and networking because this time I wasnt very compfortable with them and I didn't know them very well. I also hope to finish my final project and get a good mark on it.

Weekly Status Report #16 (May 22 - May 25)

This week was a shortened week. We started off with continuing our lottery ticket program which calculates a bunch of different things for ticket sales. The other projects that we did were with animations where we would stretch and move a picture. Other than that, we only learned about ergonomics.

I only had one problem this week. It was with my lottery ticket application. The problem was that I didnt put the code that counts the number of days in the right place so it would keep one more day than what was needed.I solved this problem by moving that part of the code underneath the exit for code.

Next week, I hope to learn more about ergonomics so I will be able to work for a long time without getting injuries. I also hope to learn more about animations so I will be able to create more interesting applications.

Weekly Status Report # 15 (May 13 - May 17)

This week, there was still a sad feeling at school because of the loss but our whole school tried to get past that and get back to work. At the begining of this week, our teacher started of lessons with a handout and a short introduction about ergonomics with computers. I learned about his stuff last year in business but it was a good way to refresh my memory. Along with that stuff, we also got a new program that used arrays which we had to create which asks for the user to input the number of lottery tickets that they sold for each day of the year. Then you would have to show the most/least amount of tickets sold, the number of days where 50 or more / less were sold, and a bunch of other things.

I only had one problem this week but it was solved quite fast. My problem was that I didnt really understand how arrays worked and how they were supposed to be used. To solve my problem, I reread the handout about arrays and I experimented on the computer with different examples. Now I fully understand how they are used and I find them very interesting and efficient.

Next week, I hipe to keep doing work with arrays and expand my knowledge of ergonomically correct ways so i will be able to live without lots of injuries. I also hope that I do well on the lottery ticket program which is being marked net week too.

Weekly Status Report #14 (May 7 - May 11)

This week was a very sad week for all of us at our school sicne we have lost one of our students. For the last two days of this week, we played games or did whatever we wanted to take our minds off of this accident. We also did this because there weren't many people in our class because of this unhappy incident.

Before that incident though, we learned about arrays and made a bunch of different programs with them and we also modified our SIN number validation program with it. Arrays allow you to identify variables without having to define each one.

In the future, I hope that everyone will be able to recovery from this tradgety and get through it with the help of others.

Weekly Status Report #13 (April 30 - May 4)

This week we learned a new type of loop to add to our knowledge. The type that we learned was the while loop. By using the while loop, you don't need to set parameters for the program to run. All you have to do is set a condition where when something happens, then the program will go past the next. To help us understand how the while loop works, we created two programs. One of them as a SIN validation program which did special calculations to see if the SIN number is correct. The other program was were the user input a bunch of marks and then the program will be able to show the highest, the lowest, and the average. We also learned how to draw pictures with straight lines but that isn't compulsory for this course.

I only had one problem this week and it was with the SIN validation program. The problem was that I didn't initialize the input so once you input the number that made it close, you wouldn't be able to open it back up since that number is still in there. I fixed this by putting inputbox="" so the program will open more than once.

Nest week, I hope we learn more about drawing pictures and different types of loops so my knowledge will be greater. Good Bye!

Weekly Status Report #12 (April 23 - April 27)

This week we learned a few new things. One of them was different careers that involve programming. For two days we made mini presentations about the research that we did previously for the communication part of our mark. The second thing that we learned was how to use the timer control. The timer control allows you to make things happen without even clicking a button. For example, we added a timer to our slide show presentations so instead of clicking the button every time to change the picture, it changed automatically. The final thing that we learned was while loops which are like for/next loops except there is no limit to when the loop will go for. Also this week, we had another test about strings and everything that we had done since the last test.

I only had one problem this week. The problem was that my program that used the while loop and checked how many times a number can be divided by two. When I first made my program, in the parenthesis that go with the "while" I put a statement that wasn't a boolean operator so my program didn't work. Then after I added a mod operator, I put a statement in the parenthesis so the program worked.

In the future, I hope that I can finish the SIN number program that was assigned (with no errors) so I could get a good mark on that. Also, I hope that I learn more about proper programming so later on in life, if I become a programmer, I will be able to create programs that don't have any mistake with them the first time that I write them. Lastly, I hope that I have done well on the test that we had on Thursday. Bye!

Weekly Status Report #11 (April 16 - April 20)

This week we learned more about the for and next loops. We only had one handout and it was for the exit for. This was the only new aspect to programming that we learned about. You use exit for when you want to stop a loop from continuing so when there is a exit for, the computer will notice that and will skip the rest of the steps and go just past the next. Other than that, we only did a written, communication assignment that was about different careers that involve programming.

There was only one problem that I encountered this week and it was a security problem. The problem was that before you save the program, you would be able to run it but right when you save it, there would be a security error with the G drives so the program wouldn't be able to run. We solved this problem by saving the programs onto our usb keys and then accessing the program from there.

In the future, I hope to learn how to add animations like fireworks so our programs will be more interesting. I wanted to add one to my guessing game but i didn't know how to soI couldn't. I hope the next week is as fun as this week too. Bye!

Weekly Status Report #10 (April 9 - April 13)

This week we concentrated on one new aspect of programming. It was loops (For/Next). Being able to use loops is a mandatory component that you have to know to pass computer science and I agree with that since loops make a potentially long code, short and very easy to understand. To help us understand loops, we would have a short lesson at the beginning of each day and then we would get a sheet with different codes that we would copy into a new program. After that, we would trace the programs to see what was happening within the program and the different variables.

I didn't have any major problems this week. A minor one that I didn't initialize a variable so every time the button was clicked to calculate the answer, the numbers would keep adding up so if the user double clicked accidentally but didn't notice, they would have the wrong answer. another minor problem that I had was that I would make lots of logical errors mainly because I wanted to rush through the programs so I could be finished before class ended. Now, I take my time and don't care if I have to work at home or have to continue my work the next day.

In the future I hope that we create some more programs that use loops so I could get practice and become as familiar with that as I am with if and else and case statements. Also I would like to get more practice with tracing my programs so soon, I won't have to ask someone what I did wrong with my program and I will be able to trace my program and figure it out by myself. This week I learned a lot and next week I hope I learn a lot too.

Weekly Status Report #10 (April 9 - April 13)

This week we concentrated on one new aspect of programming. It was loops (For/Next). Being able to use loops is a mandatory component that you have to know to pass computer science and I agree with that since loops make a potentially long code, short and very easy to understand. To help us understand loops, we would have a short lesson at the beginning of each day and then we would get a sheet with different codes that we would copy into a new program. After that, we would trace the programs to see what was happening within the program and the different variables.

I didn't have any major problems this week. A minor one that I didn't initialize a variable so every time the button was clicked to calculate the answer, the numbers would keep adding up so if the user double clicked accidentally but didn't notice, they would have the wrong answer. another minor problem that I had was that I would make lots of logical errors mainly because I wanted to rush through the programs so I could be finished before class ended. Now, I take my time and don't care if I have to work at home or have to continue my work the next day.

In the future I hope that we create some more programs that use loops so I could get practice and become as familiar with that as I am with if and else and case statements. Also I would like to get more practice with tracing my programs so soon, I won't have to ask someone what I did wrong with my program and I will be able to trace my program and figure it out by myself. This week I learned a lot and next week I hope I learn a lot too.

Weekly Status Report #9 (April 2 - April 5)

Throughout this whole week, we only worked on our pairs project. On Monday, we found out our groups and just got the setup of the programs and the names done. For the rest of the week, we worked on coding all of the aspects to the program. This program, Pizza Palace, was meant to allow the user to pick different types and sizes of pizzas (plus side orders and drinks). Then the programs will add up the total for the user to see. Also the user would be able to change the prices of each of the pizzas and sides.

This program was very complicated since used lots of different dialog boxes and there were lots of coding to do. The thing that took the most time was the naming though. We had to name all of the different tools with a correct beginning and there were way over 20 different tools that needed to be renamed and their text had to be changed. The main problem though, that we had was that when we opened the project, the numbers that we had in the dialog boxes wouldn't work right away. Instead you had to open each dialog box and click ok for those numbers to be in effect. The solution was that we needed to give values to each of the variables in the beginning when the project loads. That was the only big problem that KoolK and I had.

In the future, I hope to continue to get complicated programs like this because I like to have challenges where I have to use all of the knowledge that I have attained. These complicated programs are fun to work with. Hope more are on the way! Goodbye!

Weekly Status Report #8 (March 26 - March 30)

This week, we only created one program. This program was the payroll one. At first we the program just calculated the payroll with a specified tax and hourly rate. Later on, we added more features to it like a menu strip and a dialog box. After the user uses the menu strip to open the dialog box, they were then able to change the hourly and tax rates for 3 different groups of hours.

This program wasn't very tricky until the information from the dialog box was sent to code for the main form. The problem was that when you clicked on "ok" on the dialog box, the form couldn't read it so the output was always be wrong. On Friday, my teacher found the mistake with the program. It was in the code that was written on the page. The fix was that instead of dlgHourlyRate.Show() it had to be dlgHourlyRate.ShowDialog(). After I found this out I was able to make the Hourly rate and the tax dialog boxes to work.

I am really starting to like TIK. The more that the computer programs get more complicated, the more interesting they become and the more I have to think. I really like challenges and this was definitely a challenge. Next week, we get our groups for the group projecta nd I hope we get to choose our own groups. Bye!

Weekly Status Report #7 (March 19 - March 23)

This week, we only created two programs but hose programs were much more sophisticated and more complex that the other ones. One of them was creating a program that converted fahrenheit into celcius. At first, we made this program with a textbox that the user entered the fahrenheit temperature into and then when you click a button, it will convert it but then later, we used a trackbar (which was a new tool) to change the fahrenheit degrees. The other program was one that demonstrated different types of string functions and it used a listbox (which was a new tool). Along with those programs, we also wrote an essay about web awareness and learned about different types of variables like boolean, byte, etc.

One of my main problems that I had this week was with the string function program. while I was working with it at home, I couldn't figure out how to do some of the different functions. When I came to school the next day, my teacher helped my a lot and she taught me how to do the functions. Another big problem that I had was with the temperature program. Every time that I ran the program, there would be an error that would show up. The error was that when I made my trackbar minimum, I made it the same number as the fahrenheit temperature so it was a negative number. I soon found out that that was what was causing the error and now I know that you are not able to set a trackbar minimum to a negative number so you have to compensate that by increasing the maximum.

Next week, I would like to learn more about string functions and how to use them effectively so they can work well in different programs. I also would like to keep up my good marks on my tests since this week we also got back our second test and I got perfect. Overall, this week was pretty fun and I would like to continue making complex programs.

Weekly Status Report #6 (MARCH BREAK)

This week I didn't do anything special. All I did was stay at home. I like traveling around but I think this week I really needed to catch up on sleep and just hang out at home. I really enjoyed this week and I am not really looking forward to going back to school. Anyways, I hope that my first week back is a good one so I can get hooked back onto school and get in the groove again.

Weekly Status Report #5

This week in class we created more programs. One new thing that we did this week was using the cases. By using the cases it is easier to compare lots of information instead of using lots of if and else statements. Another thing that we learned during this week was debugging. There are three types of bugs. They are logic (the programmer has made an error in what they want the program to do), runtime (the user has input an incorrect symbol), and compiler (there is a mistake in the code). This week we also had our second test. It wasn't very hard, and I hope that I did well on it.

I didn't have many problems this week. A minor problem that I had was that I didn't really understand how to use cases. I find that if and else statements are much easier to use than cases. The main problem that I had was changing the name of the pop-up box in TIKVB11 which was the program that we handed in. At first, it would jsut say the title of the program and that seemed really plain so I wanted to change it. I solved this problem by searching through the internet. I came across as site that explained what to do but I didn't realize that I had to change the name in the bracket that outputs the results so when I put the code one line under the main message box's code, another box would pop-up after you click ok. Then I realized that the title had to be with the original code so I put it there and it worked.

In the future I hope to learn how to use cases better because i still don't really understand them. I also hope that we create programs that will use more than one group of radio buttons or check boxes which means that the programs will be more difficult. I like challenges so that is why I would like to create more complex programs.

Weekly Status Report #4

This week I only came to school for three out of the five days. I missed Thursday and Friday because of the bad weather so the busses were cancelled so i had no way of coming to school. This week, one of the things that I was looking forward to the most was getting my first test back. I did much better than I thought that I would have since Ms. Emami kept explaining to the class that lots f people had done poorly and I was afraid one of thoese people were me. On Monday, we had a lesson about software documentation. This was important because by using software documentation, another programmer could open up the project and they will be able to understand what each line of code is about. Then on tuesday, we had a lesson about if and else statements on visual basic. With these new key words, we are now able to make prgrams that can put words and numbers in order as well as have different outputs for one question (depending on what the user input). On Wednesday, Ms. Emami went around the class and marked our third visual basic programs (TIKVB2). For this program that user was supposed to be aloud to input three numbers and then have a choice between three buttons to click and then whichever button was clicked, the outcome was supposed to show the correct answer. For what we did on the next two days, I will look on the teacherweb, ask others in the class, or wait for monday to talk to Ms. Emami to see what i missed.

This week, I only faced one problem. It came in TIKVB6, I think. Well, it was the one with the plural of sheep. My problem was that I didn't know how to put more than one possibility in one line. I still don't know if it is possible but to get around that I made the different possiblilities (sheep, Sheep, and SHEEP) in different lines each starting with elseif. The only thing that stayed the same was the output message because all of those anwasers were right, it jsut depends on how the user types the answer in.

In the future, I hope to to well on the quiz on visual basic that in on thursday. Also I hope that I keep learning different key words on visual basic so I will be able to create really complex programs that could do really hard calculations.

Weekly Status Report #3

NOTE: This weekly status report is late because I accidentally put it on my first blogger account that I made for TIK instead of this one. Sorry for the inconvenience.

This week I wasn't in class for a day because of my music festivals but we didn't do much in class anyways. On Monday, we had the first test of the course about flowcharts. Then on Tuesday, we had our first lesson on visual basic. Unfortunately, the program wasn't loaded onto all of the computers yet so we didn't get to try out the program until Wednesday. The lesson only took half of the period so for the other half of the period, we worked on math and word problems. Wednesday was the first visual basic day to work on the computers but I had to go to my music festival so I was behind a bit. On Thursday, I finished the first VB program that we were supposed to make (tax calculator) . It was really cool to actually create a program. Then on Friday, I got the next sheet which had some more programs that we were supposed to create. I only got through the first two and I dint want to get too far behind so I downloaded the program at home and finished them.

I faced a couple challenges while creating my fifth program (TIKVB4) and a time challenge. the time challenge was just that I didn't want to get too far behind the whole class since if I was, then I might not understand what the we would be discussing during the future lessons. I solved this problem by just downloading the program at home so I could catch up to where everyone else is. The problems which I encountered during the creation of my TIKVB4 program was that I didn't quite understand what it was asking for, and I didn't know how to get all of the different information (first/last name and age) into one textbox. After reading the question over, about 5 times, I finally realized that it wanted the user to be able to input their first and last name, and their date of birth and from that, you would have to create a program that took that information and put it all into one textbox in a certain format. I solved my other problem (not knowing how to put all of the information in one textbox) basically by trial and error. At first I tried to put spaces and commas between the words but that didn't work. Next, I tried to put the different words into brackets but that didn't work either. Finally, I looked over all of the buttons on the keyboard and i saw the "&" button so I put that in and it worked. While I was trying to solve that problem, I also came across how to put separate words into the textbox (using quotation marks) so this made it easier when it was time for me to format the different parts of the information in the textbox.

In the future, I hope to still learn more about this visual basic program since it seems really interesting. I also hope that I learn how to make more complex programs.

Weekly Status Report #2

This week, for me, wasn't as productive as the last week mostly because there wasn't as many tasks to complete which were on the computer. Most of the tasks were just little assignments that we had to do on handouts. One assignment that was more than just a little task was the flowchart task which was given on Friday and to complete for Monday. I didn't do well on that but I learned a couple lessons from it. One of the lessons was that I should thoroughly read the question before i start it so I don't do the right thing. The other lesson that I learned by doing this task was that if I don't fully understand a question, then I shouldn't just put down an answer that I think makes sense just to get it done, I should actually look over my notes or ask someone else so i can understand more and get full marks on that task. Two more assignments that we had to do were an essay about computer ethics and a paragraph on the difference between a mainframe computer and a supercomputer.
In class we went over a lot of topics since we didn't have a lot of other assignments to do. The first thing that we did was talk about different computer terms like hardware, software, and programs. We also went over what output/input/peripheral devices, and how to classify computers (supercomputer, mainframe, minicomputer, microcomputer, and laptop). Then the next thing that we discussed was the different models of computers (simple vs. extended) and the types of memory (secondary/auxiliary memory vs. primary/main memory). Then we got a handout about the different memory sizes and a handout about pseudo code which went along with the flowchart subject. The second last thing that we learned about this week was the different types of software (spreadsheet/word-processing/database). Finally, the last thing that we learned about this week was the cryptography. This was the thing that I enjoyed the most since we got to play with those spinning wheels and encrypt and decrypt messages.
Next week we are having the test on flowcharts and I am planning on studying a lot to do good on it. Also I think that we are going to start learning visual basic and I am looking forward to it since it is new to me and I think it will be interesting to learn a type of programming language. Overall, I think that this class will become much more fun as the weeks go by and we start learning more about the actual programming language and I am really looking forward to it.

Crazy

Reporter, Peter Silverman, gets attacked.

Posting Through E-mail

Just adding a post through e-mail.

 

Weekly Status Report #1

This week was a really fun way to start off this course. The main objective of this week was to create a blog which has different features like music, videos, and hyperlinks and has an interesting blog name. Although creating the blog was our main objective, we also had little assignments and lessons dealing with the problem solving model and flowcharts.

I finished all of the work that was required for this course, so far, which were to flowchart examples, the flowchart loop examples, and my blog. This was the first that I used a blog and I found it pretty fun. I already added 4 of the extra components which include: add a Hyperlink to my post, add an image to my post, add an audio clip to my post, disable comments for one of the posts, and add a counter to my blog. Additional things that I have put on my blog are the 5 games and a banner. When I was creating my blog, at first, I didnt know how to add a video to it so to overcome that problem I tried to serach on the internet how to but I still couldn't find the solution. When I came to school the next day I saw that some of my friends already had a video on their blog so I asked them how to do it. Luckily, they were nice enough to tell me how they did it. After I learned how to do that, I realized that I might be able to use the same format of embeded code for other things like the counter so I searched on the internet for counters to add. Then I decided to add more to my blog so I used the internet to search for other codes taht I could add to my blog. I found a banner, games and a music player so I added them. The next problem that I encountered was that the games that I added were to big to put on the sidebar even though I wanted four of them to go there and one to go on the bottom like a footer. I then looked at the code and realized that the size was incorporated into the code so when I found it in each of the games, I changed the dimensions around to fit in the sidebar. When I added the extra features to my blog, I encountered another problem too. The problem was that hyperlinks kept appearing along the top of my blog. I realized that they must be from the code that was put in to get the game or banner there so I searched in the code and found where the links were and I deleted that part. One thing that I like about this course is that since we get learn lots of things on our own, I get to experiment witht he codes and wee what controls what objects.

In the future I plan to add lots more features to my blog to make it more interesting like adding photos in my favourites list and maybe adding a poll. I also have the homework that was assigned on friday to complete for monday. A goal that I have for the future is to learn more about applying flowcharts to programs and overall learning more about programming computers and how code works.

Music

Here are some really good songs. Hope you like them. (Note: Please be patient if you have a slow compter becuase then the song will load slowly too.)

Games!

Just to let everyone know, I added 1 games below all of the posts. I also added 4 games at the right side of the screen.
Enjoy. :D

All That I've Got by The Used

This is one of my all-time favoute music videos.

Feedback

Keep up the good job :-)

HAHA

Sorry can't comment on this post. :P

Colorado Avalanche

The link below is for my favourite hockey team (the Colorado Avalanche hockey team).
Colorado Avalanche Website

Funny Comic

Here is a funny comic that I found.

Welcome

Welcome everyone to my weblog! This weblog is dedicated to the work that I do in computer science.