2.am and I am still on a bit of a role with my new Windows 8 App.
When did you last pull an all nighter?
That tends to happen a lot; between overseas customers and the fact that I'm just a night owl. But it's getting a lot more taxing than it used to be.
Overnight system upgrade last year, I think.
Calling it a night - just remembered what I am doing tomorrow ...
OK really now.
A few months ago finishing up some code for a client. I will never do that again
I've never pulled an all-nighter (except for one all-night horror show at the cinema). I'd rather get some sleep and then get up at 4am to carry on. I've never done good work after 11pm.
And what are you doing today that you just remembered?
I think an unanswered question here is: define an 'all-nighter'?
I recall a few nights back in High School, being up until 7 or 8 am in an AOL chat room (or chatting with a few interesting folks met there).
I recall a night back in college where I was up til 5 am, cramming a book on programming languages with progressively worse Mortal Combat movies on TV channel I was tuned to (I honestly do not recall which was more painful).
To this day I say (a long standing mantra): "I don't drink caffeinated drinks... If I am up until 3 am debugging code... I'm up because of willpower... or desperation"... despite which my wife will frequently yell at me to go to bed ~12 or 1am if I am working on something from the couch (or basement home office).
So again I ask... how late is an 'all-nighter' for the context of this thread?
@JoshRoss, you are a better (or more forceful) husband than I... my first born is ~two months old but my wife has gone to extended lengths to make sure that I get a full night's sleep each night (including the whole yelling at me to go to bed when she thinks I'm up too late) as I am the sole bread winner in the house for the three of us... despite my willingness to take on the young'in from time to time so as to allow her an uninterrupted sleep... something that only happens when a grandparent visits and orders the mamma to bed and keeps the young'in away from her.
The best programming decision I ever made was to simply stop doing it after a certain amount of hours, no matter of how 'in the zone' or 'on a roll' I thought I was. This has saved me many, many hours of having to redo all that stuff that, after a day or two, actually turned out to be terrible.
The last time I pulled on all nighter, was when I was employed at Avanade.
We did a job at a large insurer and some bozo (me) decided to shrink the database at 1PM.
Next morning we had 60 testers coming to test the new release of the product.
Shrinking a 250GB database takes some time, especially one designed by us.
At 10PM the lights of the entire building went out, including the toilets. They could not be turned on.
At 1AM the project manager, decided that he needed to go for a #2 in the dark.
At 1:10AM we turned off our computers and moved to a different office
At 1:30AM the project manager returned to the now empty office, yelling to us on the way there how difficult wiping is, when you cant see.
At 1:45AM he phoned the program manager to explain that we have left.
At 1:50AM we explained to him, that we just moved offices, no biggie
So, finally at 4AM the database was done shrinking and testing began at 8PM.
@Maddus Mattus: We have learned to all keep small torches in the office so that when we have one of our (not infrequent enough) power cuts, we can still use the toilet which has no windows; does make it more of an adventure, though.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.