Comments on: Happy New Year! http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/ I will not fix your computer. Tue, 04 Aug 2020 22:34:33 +0000 hourly 1 https://wordpress.org/?v=4.7.26 By: Miloš http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7570 Thu, 03 Jan 2008 02:59:27 +0000 http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7570

Funny you would ask this. I actually did my new year’s resolutions for the first time ever this year. I don’t believe in starting something new only on Mondays or at the beginning of a new year, so I never had any specific resolutions until this year. A friend of mine suggested I should try it as it is easier to track your progress when your goals are written down, more visible and measurable so I gave it a shot.

I’ll let you know how it works out for me. :)

Reply  |  Quote
]]>
By: ths http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7565 Wed, 02 Jan 2008 08:41:09 +0000 http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7565

I really do hope nobody does epoch calculations with signed 32-bit integers anymore in 2038 ;).
anyway: did anyone remember big crashes in 2001 when the decimal representation of the epoch went to 10 digits?
(Sun Sep 9 03:46:40 2001, perl -e ‘print scalar localtime(1000000000)’)
I remember one minor problem in a Tivoli application helper script when an epoch-parsing script in perl used \d{9} instead of the correct \d{9,10}.

happy new year everyone who’s inclined to believe in the gregorian calendar. for all others refer to calendar converters like the collection at nabkal.de (german only, but quite complete).

Reply  |  Quote
]]>
By: Luke Maciak http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7562 Wed, 02 Jan 2008 03:34:32 +0000 http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7562

@Starhawk – fortunately a lot of linux distros already use 64 bis to store the unix timestamp. This one will be much less work than Y2K and the daylight savings thing.

@Matt` – nope, we’re not resolving – we just choose not to make resolutions. And since resolutions ought to be made prior to the new year then we are in the clear. :)

@Zack – good luck. I’m horrible at luck based games. I have a natural -3d6 to all luck based rolls – it’s like a curse or something. :(

Reply  |  Quote
]]>
By: Zack Sloane http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7560 Wed, 02 Jan 2008 01:50:24 +0000 http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7560

Mine is to try to $5000 this year playing poker! Tonight I am hittin the casino to get started on that goal. I already made $500 tonight online, lets hope I don’t lose it tonight! :)

Reply  |  Quote
]]>
By: Matt` http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7559 Tue, 01 Jan 2008 22:52:00 +0000 http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7559

Is resolving to not make any resolutions equivalent to dividing by 0?

Or does it just mean you broke your resolution in record time

Reply  |  Quote
]]>
By: Starhawk http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7557 Tue, 01 Jan 2008 17:28:40 +0000 http://www.terminally-incoherent.com/blog/2008/01/01/happy-new-year/#comment-7557

Anyway, we all know that the universe as we know it ends on Tuesday Jan 19, 2038 at precisely 3:14 am GMT. I will leave it as an exercise to the readers to figure out why.

Ya gotta love short sighted programmers.

On January 19, 2038, UNIX-based programs and UNIX-like operating systems will run out of time. To be more precise, at 3:14:07 GMT, UNIX will be exactly 1 billion seconds old.

Well happy new year Luke. No resolutions for me no use setting myself up for failure. haha.

Reply  |  Quote
]]>