Whoa week!
Ah, and another week comes to an end. Seems like Murphy postulated his law with the technology people in mind, especially the computers related ones. For those who are still ignorant about this wonderful law, it goes something like this: If something can go wrong, it will. There is it. The philosophy of life, captured beautifully in a few words. And yet, it proves true more often than not for all us Computer Science undergrads! What would you say when on the night before submitting the first phase of the compiler project, the front end and the back end of the applications just wouldnt connect and fail to co-exist amiably? What should be done when on the day of the demo, I couldnt even manage to display the file in a little window? And then, treat J# as similar to C#? Or when the application goes bang right in front of the TA when he runs it for the first time? The most embarassing part is that there was a teensy thing overlooked that wouldnt let the file display in that little window, and that I came to know of after the demo. Ah, life. The TA was lenient enough for postponing the demo till the next day, as I squarely lay the blame on the computer. Ofcourse, there wasn't any problem with my application. There just couldnt be! And finally, the demo went smooth. Murphy's law can go pop in his face, for all I care!
6 comments:
no1 is interested in ur this post isliyeh new post kardo :P
:( nobody is really interested
mein sad hogaya :'(
agar wrong nahi hoga toh right kaise hoga =P
Hahaha! Hear a dada-abba speaking :P
And this is why "XP" (Extreme Programming) methodology rocks. You'll never face this kind of wierdness in your programme if you follow that methodology. At least it works for me!
Ofcourse it does, ChalkJee, but you know, the project is a course project, and the submission was to be done of its phase one, and there were only two days.
Enough to understand what is required and just to construct it.
:)
Post a Comment