Ughh. Codes.

I don't believe in paper coding. At all.

I don't mean pseudocodes. In fact, I like pseudocodes (interestingly, I NEVER forget the semicolons while pseudocoding) ...they are great for logic planning, as well as killer ice breakers if you want to get into the circle of the computer minded/geeks/nerds. I mean, if you go up to an engineer and say "Hey, knock knock?", you could well receive a cold puzzling oh-my-gosh-some-psycho-is-talking-to-me look. Hence you need to speak the same language:

{

printf("Knock knock");

gets(response);

if(response=="Who's there?")

{

joke();

}

else

{

printf("Oh my gosh, you just plain don't get Knock knocks, do you?");

give_up_socialising( );

}

}

Anyway, as I was complaining, paper coding. Yes, what is up with that? Honestly, I don't believe in coding without at least 1 reference book next to you and 2 browser windows opened (one on API, and another to Google). Then of course, you need plenty of room for hair pulling, Doritto grabbing, whatever else to take your attention off the code and lastly, a huge screen long enough to display the millions of compilation errors without having to press the PgDn button (yet to be produced). Pen and paper coding simply does not work.

Why am I complaining? Well, I could very well be asked to paper code in C/C++/JAVA which I claimed I could do in the next 2 hours. Wish me luck.

(By luck, I mean be able walk out there with grace, as opposed to being thrown out with good bye and never see you again)