Re: You know you code too much when...
46. When you walk to work, you think in assembly language: mov EAX, to_sidewalk, mov EBX, to_street, ...
47. Whenever you write research papers, you always have to include some objective-C code. After all, we're talking about apple mac apps, right, and we have to write them, right?
48. Whenever your boot manager fails to boot an operating system, you have a nervous breakdown because your compiler will throw an exception and you won't be able to catch it.
49. When GRUB drops you into its shell, the first thing you try is some assembly code. After all, boot loaders understand direct processor assembly, right?
50. Whenever windows displays a blue screen, you always say, "Why didn't it declare that variable?"
51. When someone asks, "Can you open the window?" You always wonder what binary value to set the windows opened bit to.
52. When you fiddle with the firmware of a device, you always wonder how to enhance its capabil
ity.
53. When you are having a casual conversation, you always push each question on the stack and pop it off after the answer is moved into the proper processor register.
54. When your entering passwords, you do dangerous memory allocations and deallocations in your head for each bit of the password.
55. When you drink a soda, you always think that your drinking the successful compilation of a program's success, and you check the exit and return codes to make sure before taking another sip.
56. When you enter your username, you always ask yourself, "What method does it call to check user names?"
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
