Irony

Okay, here's the thing. I am not good in compiling programs. I have a hard time understanding some logical reasons behind every code and why they are written like that. I have, like, thousands of silly questions to be asked to the person who taught me before I could say "Oh, I get it". Now that I've choose to engage myself in this war of object-oriented programming, I'm pretty much ambivalent whether I will survive this battle as much as I enjoyed figuring out ways to overcome the uncertainty in handling the Debit and the Credit thing.

A snippet from my Java Programming book.

Yes, it's true. I came from non-CS background where most of the things I deal with were numbers, papers and calculating instruments. However, I do know how to code. I mean, most of the time, I do get my codes working correctly as I wanted; displaying the predicted output but they were only temporary. I fail to act like a sponge and ended up being a loser hours later. I forgot every explanation told by the lecturer in the lab as I stared helplessly at my laptop's screen 4 hours later in my room, trying to compile a freaking simple program that a nine years old kid like him could easily compile in less than 20 seconds.

I'm not the kind of girl who easily fall short of herself. Whenever my mind pulls a 'STOP' signboard to a certain unacceptable input and that I can't solve it alone, I let people help me see things clearly so that I could find the key to unlock the idea myself. It was always motivating to do so but not this time. Here's what I keep getting whenever I said I'm not good with programming:

"You are a Software Engineering student... Duh?"

How irony. I think I do fall short of myself this time.

Untitled

- It's gettin' late... So I'll catch with u later?

| Ok... Catch with u later in 6 months time, Nad. |

- 6 months?

| Yelah, lepas ni u akan hilang balik kan? |