Showing posts with label desk check. Show all posts
Showing posts with label desk check. Show all posts

Friday, January 14, 2011

In which Pearl works hard to finish the CA!

Konbanwa, minna-san!

I'm pretty tired today, but that's alright. It's Friday, so I'll have time to catch up on my sleep over the weekend. Hopefully.

Today Mr. Arkin was away because he wasn't feeling well. Zarin-dono and I were chosen to be the Student Hosts - what fun! Actually, I was pretty nervous at first because I wasn't exactly sure how I should take on the task. Nevertheless, Zarin-dono was very brave and took the lead. Ha.

I feel like class is getting shorter and shorter. I was working on the Glossary today, and soon enough, it was time to back up and get ready for the next class. I'm almost done - I just have a few more definitions to write out. I need to finish by tonight, so Tasfia can put everything together over the weekend. Then, Lisa and I will proofread and edit the entire manual by Wednesday. That's the plan.

Things are coming together quite nicely. There's only a few more sections that need to be finished.

As for other CAs, I've gotten my English one over with. The only thing that's left to do is write an in-class reflection, and that will be done on Monday. In French, we're making presentations about environmental issues. My group is talking about deforestation in British Columbia. There's no Science culminating, but Mr. Pourkhatai is giving us a big project related to Astronomy. Sigh.

I feel like there's no time to study. If I have spare time, I plan on finally getting to typing up my French and English notes and hopefully start on either Science or ICS.

Below is a video (courtesy of YouTube) of a new song from JASMINE. She's a Japanese singer. I really like her style. Ever since I heard the radio rip a couple of weeks ago on the rotation site I use, I've been wanting to get the song. The official release date is February 2nd. I can't wait!

ONE - JASMINE


Wednesday, December 15, 2010

In which Pearl struggles to write a code

Konbanwa, minna-sama.

As usual, I'm feeling very tired and lethargic. Add in some stress because the majority of my classes are "behind" the other Grade 9 Pre-IB classes of said subject, and you have the perfect formula for exhaustion. If it's possible to get more than 7 hours of sleep a night in the next few days, I'd like to take advantage of that. Otherwise I might really fall asleep in Science. (And no, I absolutely cannot afford that!)

I think my overall average went down a lot, and it's got me worried. I already knew that my Science mark would drop, I just didn't expect it to drop so much. I'm even dropping in ICS, and I feel horrible, especially after Mr. Arkin gave his speech about expecting us to get over 80% on the recent programming test. I made stupid mistakes...very stupid mistakes...

Anyways, today we continued working on the "Follow the Bounce" program. Last night (this morning?), I had gotten a large part of it done. The only problem was that there were (I'm exaggerating here) a million loops, so that even I got confused - and I was the one who wrote the thing! So, yes, when Randi came over and told Zarin and I that the program only needed to consist of one loop...I...cried. All my hard work, gone! Well, it's nothing to lose sleep over.

By the end of the period, I had gotten a pretty good idea of how to do it. Of course, that included a ton of desk checking (in my head, because it would take too long to do it on paper) and tracing the execution (with the computer). Now, I only need to fix a little glitch and it'll be perfect! Of course, I could never have gotten this far without help! Thank you to everyone who helped me, you know who you are!

I really like this program (staring at it is fun!), so I'm going to create an executable for it. I want to send it to my mom so she can see it (and maybe even show it off to her colleagues at work). Teehee.

For homework, I need to start on the "Window-edge Tracker" program. I have a pretty good idea about how to do it, but I don't want to spend an excessive period of time on it, since I have a big essay for English that I need to finish. I also agreed to editing Zarin-dono's essay (and I'm perfectly happy doing so - I don't mind at all)!

So, I'm off to work now.
Mata ashita, minna-sama!

Friday, December 10, 2010

In which we achieve our goal!

Konbanwa, minna-san~
I think I was still "drunk" from International Night this morning. Heh, not even. I was "drunk" the entire day. I'm going to sneak in a fangirl moment here and say "Oh my God, the Korean groups were so awesome!!!" (Y'know, I'd replace "awesome" with another word [that starts with "h" *wink*] but it's probably not a good idea to say that here.) Ha, now I have renewed respect for Asian boy bands. *cue fangirl squeal* The song's still stuck in my head: Again and again and again and again...

On the other hand, I'm exhausted. After I got home and ate dinner (yes, I get home almost right before dinnertime) I went to sleep. I woke up at 9:30 PM, mentally kicking myself for not writing my blog first. Then again, the minute I go on the computer I won't be able to get off of it for a while. So, yep, that's why I'm doing it now.

*cough cough* Anyways!
Today was the last day we had to review programming in our groups. As I mentioned in the blog title, I think we achieved our goal. My group went over all the Programming Concepts noted on the handout Mr. Arkin gave us quite a while ago. I made sure I understood everything there, and if there was anyone who needed something to be explained to them, I tried to help. (Hopefully they understood after my efforts!)

I love helping others. *smile* I want to be an elementary school teacher, so it's actually helping me prepare for the "challenge" as well.

On another note, I need to start preparing for exams and culminating. Over the break, I plan on taking all my binders home and creating study guides for each one of my subjects, especially Science. Hah... That's what made me "sober". Mr. Pourkhatai returned out Ecology tests today after school, and I got a...horrible mark that will undoubtedly bring down my average.

Dakedo...oyasumi, minna-san!

---

Translation: So...good night, everyone!

P.S. For anyone that's interested, there's a Japanese boy band called NewS (also, NEWS, News) that's actually good. Sorry, I used to hate boy bands in general because they sang about...fickle concepts. Like love. (Dear God, I must sound morbid now.) But yeah, they sang for the seventh One Piece movie. It's called "Sayaendo". The translation's cute.

Wednesday, December 8, 2010

In which we learn about procedures

Konbanwa, minna-san!
I...get obsessed with different series very easily. Sometimes my love for a certain series dies out. (For example, I used to adore Hot Gimmick, but now it's...meh. It's not like I don't love it anymore (I mean - who can resist Ryoki-sama? *wink/fangirl squeal*), but it's just not as important to me.) But at other times, I will continue to love that series forever and ever... Like Inuyasha. I started watching it, what, six...years ago? I still adore it. And FullMetal Alchemist, which I started watching at around the same time. Of course, I absolutely cannot forget Detective Conan/Case Closed~! I'm a huge mystery/detective fan, so I love this one. Right now, I love Durarara!! It has a really unique/amazing/epic/addictive storyline and even more unique/amazing/epic/addictive characters. I don't want to stop loving it...


From left: Izaya Orihara, Anri Sonohara, Mikado Ryuugamine, Masomi Kida, Shinra Kishitani, Shizuo Heiwajima. The figure in the moon is Celty Sturlson, a dullhan.
Durarara!! (c) Ryohgo Narita
 Ah, but these are simply the ramblings of a crazy fangirl/writer. To get back on topic...

According to my Programming Glossary, a procedure is a subprogram that performs a defined task. It is very similar to a function. However, a procedure does not have a result (because it's not returning a value) and it can have zero or more arguments. An example of a procedure with zero arguments looks like this:

procedure sayHello
     put "Hello!"
end sayHello

sayHello

This code outputs "Hello!"
However, you can "upgrade" it, using an argument. This code will output "Hello, Shizu-chan!"

procedure greetUser (greeting : string, userName : string)
     put greeting + ", " + userName + "!"
end greetUser

greetUser ("Hello", "Shizu-chan")

Simple, ne? *smile*
Of course, if this was Izaya-kun speaking, Shizu-chan would say: "Get out of Ikebukuro!!!"
D'awws, we love you, Shizu-chan~

You can also ask the user to give you the greeting and name. However, then you must make greeting and userName variables (within the procedure, if that makes sense).

procedure greetUser (var greeting : string, var userName : string)
     put greeting", " + userName"!"
end greetUser

var greeting : string
var userName : string

put "Greeting? " ..
get greeting : *

put "Name? " ..
get userName

greetUser (greeting, userName)

Got it? *smiles again*

Well, I hope that explanation was plausible. I'm generally horrible at explanations (and you wonder how I'll ever become a teacher).

Anyways, after we were taught how to create a procedure, we evaluated ourselves on our understanding of programming. Then we got into groups based on our evaluation. By Friday, Mr. Arkin wants us to fully understand all the concepts of programming! With a bit of work, I'm sure we can do it~!

Ganbatte, minna-san~!

Saturday, November 27, 2010

In which Pearl bows down in shame

Uwaah, gomen ne to shimimasen, minna-san! I forgot to write my blog yesterday! It was the Girls about Girls sleepover, and I went to Cinye's house to pass the time. I completely forgot about this, and I even thought I did it until Zarin-dono reminded me just about two hours ago. Grah... Again, I'm so sorry! *goes into seiza position and repeatedly bows down*

Yes, er, well, on Friday we got yet another work period. The night before, I was working on Repetition Assignment 13. I had finished the basic outline, but I needed to fix a certain (very annoying) glitch. It took me the entire period, but I managed to do it and print out the code! (With about five minutes to spare)

Zelin asked if he could desk check it, so I let him. And when he returned it, he told me that I got the Senior ticket price wrong. I had written "const SENIOR_TICKET_PRICE := 7.25", but the correct price is $7.50! Oh, how stupid I felt. I felt even more stupid after I noticed that I had copied down the exact question from the website, which included the prices. Grah... I must fix that before Monday.

On another note, I'm going over to Lisa's house tomorrow (Sunday) to study for both ICS and French - we have tests for both of these subjects coming up the following week.

I think that's all I have to say. I'm going to sleep now, as I need to get up early to finish my homework. (Plus, my mom wouldn't let me go if I didn't go to sleep right after I finished typing this up) Grah... I have to finish my PP article, do my English (which is actually not that hard), check to make sure my ICS binder is up-to-date, and write out a Science Lab Report (due Tuesday, so I can put that at the bottom of my list - for once).

Can I say a little something about the sleepover?
It was awesome! My group leaders were hilarious, and I laughed so hard my cheeks hurt! The dinner was delicious - lasagna and salad, with a side of bread. We even got cupcakes and chips as evening and midnight snacks (respectively). And there was karaoke~! The only part that I didn't like was that I got a headache at around 9 PM, and it got worse as the night progressed. It's probably due to lack of sleep - after all, I had gotten a total of 17 hours of sleep the previous three days. I took a nap at around 10 PM, woke up at 10:30, then went back to sleep at midnight. I didn't watch the movie.

I woke up numerous times in the middle of the night. The first time I woke up, the movie had ended. The second time, I heard these banging/popping noises. I got so freaked out! My first thought was, Oh my gosh, it's a gunfight. Then the logic kicked in, and I realized that if it was, then everyone would probably be screaming. I concluded that someone must've been setting up equipment for Saturday, and bouncing balls (some of them make a scary sound!). So, I went back to sleep. I woke up again to hear the same noise. I was a bit more awake then, so I decided that it could've been someone's air mattress. I went back to sleep. The next time I woke up, it was five minutes before 7:30 AM, and we were going to get up anyways. Hm.

Okay, this wasn't really "little", but I just had to talk about it. I had such a great time, and next year I want to be a leader!

...I'll shut up now. So, um, see everyone on Monday!
Ja ne!

Thursday, November 25, 2010

In which we spend the majority of our time talking

The day started off with Mujtaba informing the class that we had the choice of taking Latin instead of French to get our Language credit next year. I knew this already, because we are in the same French class, and our teacher, Mr. Vetranos, was the one who told us about it. Personally, I'd love to take both. I've been wanting to learn Latin since Grade 3, but I don't want to stop taking French - after all, I've already spent five years in the Extended French program, so why drop it now?

Mr. Arkin told us about how valuable it was to know multiple languages. Being bilingual, trilingual, etc. is very helpful in many different aspects of life, especially getting a job. By the time we finished discussing this, half an hour had already passed. (Yeah...being worried about how much time we would have to actually work on our Repetition Assignments, I kept glancing at the clock. I would've looked at my watch, except it broke. Two months ago. *cry*)

So, after we closed the "forum" on languages, Mr. Arkin provided us with three points that will help one become a better programmer.
  1. Read with precision.
  2. Break a solution into an ordered set of steps.
  3. Visualize contents of memory.
He suggested we read our code to another person, while explaining what each symbol or keyword does (for the first point). Zarin-dono and I sort of do this - we're halfway there. Before each one of us prints out the code, we switch places to take a look at the other's code, pointing out anything that is peculiar or incorrect. Then, we print the code out. This is great, because we save both paper and toner.

I do break a solution into an ordered set of steps when I program. I write half of the documentation section (programmer, date, file name, purpose), then before I do anything else, I think about what I will do. When I have a basic outline of the steps needed to reach the solution, I start writing the program. Like Mr. Arkin previously suggested, I start with the input/processing section. Every time I finish typing out a major action, I make the necessary changes or additions to the declaration and/or initialization sections.

I don't visualize contents of memory unless I am desk checking my code. However, after I do a test run (of my program), I look back at what I inputted and mentally check to see if the processing is done correctly.

---

Then, Mr. Arkin gave a brief demonstration of three ways Repetition Assignment 8 could've been done (for a certain part of the code).

Method 1
if integer > 0 and integer mod 2 = 0 then

Method 2
if integer > 0 then
  if integer mod 2 = 0 then
  ...
  end if
end if

Method 3 (using a boolean expression)
positive := integer > 0
even := integer mod 2 = 0

if positive and even then

The last one is cool, but it requires more variables. If I was writing the program, I would most likely use Method 1 because it is the simplest and most straightforward (in my opinion) out of the three.

---

When we got to go to our computers, we had fifteen minutes left. I barely did anything, because I needed to check over some other stuff.

All our programming assignments are due on Monday. I finished everything, but I'm not sure if I have all the codes printed out. Derr. I need to make a checklist (though  I'd probably lose it anyways).

On another note, tomorrow is the Girls for Girls sleepover. I won't be home until Saturday afternoon (I'm going straight to the library, then dance class after I leave the school.)  I'll do my best to write my blog entry tomorrow afternoon, but if it's not up, you know why. I promise to write it the minute I get to the library on Saturday, though. *smile* I'll make a mad dash for one of the computers!

I think this is the longest blog entry I've written so far, ne? I'll stop talking (typing?) now.

Ja ne, minna-sama!

Wednesday, November 17, 2010

In which Pearl perfects Repetition Assignment 6

I'm going to make this short, as I have to finish my science.

Today we switched our codes for Repetition Assignment 6 with a partner and performed a code analysis and desk check on it.

I was partners with Alisha and Randi, and...they didn't suggest anything. So! I asked Mr. Arkin! He made some suggestions and informed me of a problem I had with it - my program didn't guard against 0! (I think that's what it's called) Neither Zarin nor me could figure it out, so we asked Hannah for help. Thank you, Hannah! I really appreciate it!

By the time we were finished, there were only fifteen minutes of class left. I started Question 8, but I didn't get far. Grr... For once, I'm going to do my Computer Science homework last, since I need to print out my science stuff.

How short... Ah, whatever. Until tomorrow, everyone!

Thursday, November 4, 2010

In which we do a desk check

Aw man, I thought I already wrote this. Who knew desk checking could take so long? I'm so tired...

Well, the title is self-explanatory, isn't it? Today, we focussed on desk checking. Mr. Arkin gave us a copy of a model answer for Selection Assignment 6, and we were supposed to individually trace the execution of it. Of course, if we needed help, we could always ask a classmate or Mr. Arkin himself.

For me, it was relatively easy - just time-consuming. I performed the desk check three times, once for each possible route. (In which the conversion was cm-to-in, in which the conversion was in-to-cm, and in which there was an error when inputting the conversion choice) The biggest problem I had was remembering that the computer types in pencil, and the user types in ink. There has been many a time when I wrote the user's part in pencil and had to erase it and rewrite it. *sigh*

Then, we got into groups of four and put together a list of features that the code (for Selection Assignment 6) had. Mr. Arkin provided us with a copy of the  programming guidelines, so my group used that as a template. I tend to write titles and headings in print (because it's easier to discern it from the actual content), so it was hard to get rid of that habit. However, I made sure the actual points were in cursive. Besides, I normally write in cursive...when it's not a title or heading. *sweat*

It seems like I'm writing my blog entries later and later now. I keep thinking, "what happened to the time?" .

I still have to finish doing some research for Science and further memorize my script for French (our presentation's tomorrow!). But before I do that, I'm going to check the Daily Log in case I forgot anything else.

On a completely different note, my friend introduced me to a website where you can chat like the characters in Durarara!! do. You can find it here. They even have the same icons! It's too bad Shizu-chan never enters the chatroom...I'd love to use his icon, since he's my favourite character and all. *smile* I guess I can pose as Kida-kun (Bakyura) or Izaya (Kanra). If I want to be loved by Shizu-chan, that is...and I do...I really do...

Sorry for the above paragraph. I guess it sort of wasted your time. *wince*
I'm sorry! *bows down*
I'll shut up now.

Until tomorrow!
Ja ne, minna-san!

Monday, October 25, 2010

In which we learn how to desk check

Oh, phew, I thought I forgot to write a blog entry on Friday. *wipes sweat off forehead*
Now that my fears are calmed...

We might actually get to go to Anime North!!!

*fangirls*
Let me have a moment to celebrate.

Okay! Back to computer science. Today we learnt how to "desk check" our programs. In other words, we would put ourselves in the place of the computer and do whatever it would do. (If you want a fancier explanation: "We are tracing the execution of the program") Although it's a pain to do, I think it pays off in the end. If, for example, you have no idea why Turing finds an error, you could do this yourself and it'll probably solve the problem. Useful, ne?

On another note, I finished the Table Programs quite quickly. They weren't that hard to do! Now, I have to preview "Selection". Heh...programming is fun!

Tomorrow, I'll be away for another X-Country meet. This time it's the Metros! I can't wait! Of course, I don't expect to make it to OFSAA. I barely made it to the Metros, anyways. Well, I'm off! I still have to email quite a few people, and I haven't even started any of my other homework! *cries*

Ja ne, and see you all on Wednesday!

P.S. Yes, Zarin, I'll use "in which" for a very long time. Karin influence! Go read Chibi Vampire, and you'll understand.