berangkat ngantor 15 menit lebih awal, dan efeknya sampe kantor 30 menit lebih awal... segitu jauh bedanye..

hmm... novizki malah punya contoh lebih gawat lagi... kalo dari bintaro berangkat jam 6:15, sampe pancoran jam 8:30... kalo berangkat 30 menit lebih awal (5:45), sampe pancoran jam 7:15...

dude... kalo dipikir-pikir, di jkt gini sehari rata-rata duduk di belakang kemudi itu sekitar 3 jam-an... no wonder si noviz rela spend millions buat ngebenerin sound system di mobilnya...

anyway, dapet forward-an dari zainal yg menurut gue quite funny :

• "what we need is less people running around and telling everyone else what to do and more people actually writing code." -- linus torvalds [anti-management banget :) ]
  
• progasm: the feeling you get when your code works the first time... [hmm.. kalo compilernya turbo assembler dan file sourcenya org.asm, mungkin iya ;) ]
  
• all programmers are optimists. perhaps this modern sorcery especially attracts those who believe in happy endings and fairy godmothers. perhaps the hundreds of nitty frustrations drive away all but those who habitually focus on the end goal. perhaps it is merely that computers are young, programmers are younger, and the young are always optimists. but however the selection process works, the result is indisputable: "this time it will surely run," or "i just found the last bug." --frederick brooks, jr., the mythical man month [and programmers who have found out that truth will be promoted to be a project manager :P ]
  
• how does a project get to be a year late? ... one day at a time. --frederick brooks, jr.
  
• a conclusion is the place where you got tired of thinking. --anon [duh!]
  
• a slower system is better than an incorrect one. --mark diekhans [how about slow and often-need-a-reboot-os ? ;) ]
  
• ...one of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their c programs. --robert firth [argh.. i give up.. i dont understand this one]
  
• any sufficiently advanced technology is indistinguishable from a rigged demo --andy finkel [lol!!!]
  
• if computers get too powerful, we can organize them into a committee... that will do them in. --bradley's bromide [dang.. 2 to 0]
  
• debugging is anticipated with distaste, performed with reluctance, and bragged about forever. --button at the boston computer museum
  
• for every problem there is one solution which is simple, neat, and wrong. --h. l. mencken
  
• ignorance simplifies any problem. --r. lucke
  
• if the code and the comments disagree, then both are probably wrong --norm schryer [o man, pls.. my stomach is hurt from too much laughing x) ]
  
• never put off until run time what you can do at compile time. --david gries, in "compiler construction for digital computers"
  
• reliable software must kill people reliably. --andy mickel [hmm.. who codes for laser guides on gbu bombs?]
  
• the most effective debugging tool is still careful thought, coupled with judiciously placed print statements. --brian kernighan (1978) [dude...]
  
• the most important question when any new computer architecture is introduced is 'so what?' --someone in comp.arch
  
• though a program be but three lines long, someday it will have to be maintained. -the tao of programming
  
• laws of computer programming :
  
  
  • any given program, when running, is obsolete.
    
  • any given program costs more and takes longer.
    
  • if a program is useful, it will have to be changed.
    
  • if a program is useless, it will have to be documented.
    
  • any given program will expand to fill all available memory.
    
  • the value of a program is proportional to the weight of its output.
    
  • program complexity grows until it exceeds the capability of the programmer who must maintain it.
    
  • make it possible for programmers to write programs in english, and you will find that programmers cannot write in english.
    
  
  
• on a clear disk you can seek forever
  
• unix was never designed to keep people from doing stupid things, because that policy would also keep them from doing clever things. --doug gwyn
  
• weekends were made for programming. --karl lehenbauer [thank god those days are over for me...]
  

that same email stated that it's very easy to shoot yourself in the foot using assembly language.. i dont know what that means, but if my assumption is right i guess a code like this will do :

mov ax, 0000
push ax
mov ax, ffff
push ax
retf