• Ken B. (unregistered)

    Well, in the database I use, I would just pass the date and negative-two to the ADDMONTH() function. But who needs such niceties, when you've got a PHP god on your team?

    And the "date" is varchar(5) because he's planned ahead for the "y2k+100 bug".

  • (cs)

    GOD DATE MANGLING!

    That's almost what I would have exclaimed if I had to deal with this code.

  • douglas (unregistered) in reply to QJo
    QJo:
    Somebody remind me of the psychological phenomenon that stupid people are too stupid to know how stupid they are, while wiser people are clever enough to know they're not really all that clever. Therefore people who think they're as clever as "god" must be the stupidest people in the world.
    There are the people too stupid to recognize their own stupidity, and the people smart enough to realize they're not really all that incredible. And then there are the people that really are ridiculously smart and know it.

    So, if someone says he's as clever as god, all that really tells you is that he's not in the middle. He could just be stupid, or he really could be that smart.

    Then again, stupidity is more common than that degree of intelligence, so it's not a bad assumption that a supposed "god" is probably stupid.

  • dguthurts (unregistered) in reply to bertram

    [quote user="bertram"][quote user="dguthurts"]SELECT <explicit list of fields>[/quote]

    [quote] I love these people that just blindly repeat the claim that "SELECT *" is somehow evil, without any kind of understanding of whether is actually is, or why it could be.[/quote]

    Not evil. As noted previously, lazy and not good practice

    http://www.sql-server-performance.com/2001/sql-best-practices/

  • Spoc42 (unregistered) in reply to Dramocles
    Dramocles:
    Reminds me a bit of a versioning system I designed when working for a now-defunct big box chain. We'd use a character representing the quarter of the year (A-Z starting in a specific quarter of a specific year), and two digits to represent the day in the 99-day quarter of the year (because some programmer's years aren't metric, but at least they have a nice round number of days [400]). The lead developer pointed out it not only wasn't Y2k compatible, it would blow up in 1997. "Yeah,", I replied, "but we both know we won't be working here for anything like that amount of time..."
    When I started programming at the beginning of the 80s, working for a major Swiss bank, they were already taking steps to combat the Y2K problem, converting all dates to 8 digits. With that training, I have always had my dates with long years. Some organisations look ahead a little more than others.

    captcha: secundum = near instantaneous stupidity

  • (cs) in reply to The Poop... of DOOM
    The Poop... of DOOM:
    I'd go with a timestamp instead of a Date, but that's just my personal preference. I'm just more comfortable with PHP's timestamp handling than with its date handling. Plus, there's also something reassuring about just pulling an int in from the DB, instead of some object.
    </facepalm>

    Man are you ill-informed. The TIMESTAMP and DATETIME field types are stored using the same 'YYYY-MM-DD HH:MM:SS' format. There are two differences between them: 1) TIMESTAMPs are stored in UTC, but retrieved in the server's current timezone, and 2) TIMESTAMP has the 'ON UPDATE CURRENT_TIMESTAMP' event.

    That said, if you really wanted to make your life more difficult, you would store integer times as UNSIGNED INT (or BIGINT, depending on how far into the future you wanted to store times). But, doing so would require convoluting your SQL queries to do date/time comparisons:

    SELECT * 
FROM myTable 
WHERE DATE_FORMAT(myIntTimestamp, "%Y-%m-%d %H:%i%s") < NOW();

    And that's just a simple example! Start throwing in the logic to compare months, years and days; with some DATE_ADD/DATE_SUB and whatever other business logic that you need, and you're just asking for a front-page WTF.

    The right tool for the right job.

    PS. You really should RTFM:

    TIMESTAMP DATETIME

  • No One (unregistered) in reply to Matt Westwood
    Matt Westwood:
    Picoseconds since the Big Bang is probably more appropriate. If we need to know how many that is, just ask god. He's in the next cubicle.
    Don't you mean Planck time since the Big Bang?
  • Alex (unregistered)

    So what? $yearmonth passed in from the front end must be between xx03 and xx12. It works 12 months out of the year.

  • (cs)

    A "PHP God" is more like how the cavemen saw fire and the weather as "gods". Me no understand, must be god's work. Me listen to god.

  • Alex (unregistered)

    @myself. It's obviously not supposed to show the LAST 3 month of data, but 3 month of data.

  • Dani (unregistered)

    You know a varchar has to hold NULL character even if its in max length? so it has to have 5 characters varchar to hold 4 character string. alternatively he could used (fixed) char field with length of 4 but thats another story.

  • Childish (unregistered) in reply to hoodaticus
    hoodaticus:
    JiP:
    imgx64:
    TRWTF is the base-12 calendar, obviously. We should move to the decimal system.
    Actually, Napoleon tried something like that once. 10 hour days, 10 minute hours, 10 second minutes. Sadly, the masses rejected this unifyingly brillant concept and it didn't catch on.

    Why don't we actually move to a hexadecimal system?

    For that matter, why don't we move to a unary date system and count the hash marks since Genesis Chapter 1?

    Actually, I think the Romans meant to have a 10 month calendar. Look at the Latin names:

    September :- sept=7 October :- octo=8 November :- nova=9 December :- deca=10

    The Moon just circles the Earth too many times in a year.

  • Childish (unregistered) in reply to Dani
    Dani:
    You know a varchar has to hold NULL character even if its in max length? so it has to have 5 characters varchar to hold 4 character string. alternatively he could used (fixed) char field with length of 4 but that's another story.

    A SQL VARCHAR(N) has at most N characters. It is represented in the DB any way it wants, per the standard.

    Your database server (or client) handles data type format for you. Then, the string gets exported to the client language as needed.

    For example, PostgreSQL uses "Pascal strings" with a leading length byte for all character types internally. There's no NUL character terminator.

    A C/C++ client must write the VARCHAR(N) characters to a buffer with a NUL byte. So, VARCHAR(N) means char my_str[N+1];.

  • Rawr (unregistered) in reply to Dani
    Dani:
    You know a varchar has to hold NULL character even if its in max length? so it has to have 5 characters varchar to hold 4 character string. alternatively he could used (fixed) char field with length of 4 but thats another story.

    Another situation where I just can't tell if I'm being trolled. I'm biting again, if you guys got me twice in the same day I'll be mighty upset.

    Anyway, when you declare varchar(N) in SQL, you're setting aside space for N characters. There is an external integer that tracks how much of that space you actually use. There is NO need for a NULL terminator.

    Protip: If you're storing information that will ALWAYS be a set number of characters (say, Social Security Number of 9 digits), storing in char(9) will have you 4 bytes per row compared to varchar(9).

  • Anonymous (unregistered)

    TOWTF (The other WTF) is that Lori seems to have a problem with using php, javascript and imagemagick to generate graphs. If you want it server side and the company uses php, you use php. If you want the graph to be interactive, javascript is an option, and in order to generate the graph, imagemagick makes as much sense as HTML5.

  • (cs) in reply to Rawr

    [quote user="Rawr"]

    1. Why are we hitting the database for something as simple as a month? There are very few reasons why we need to hit the database for this. [/quote] You aren't hitting the database for something as simple as a month. You are getting the data stored for a particular month.

    [quote user="Rawr"] 2) Why are we storing months in a database table in the first place? Months are available in the database, and they are available for a multitude of regions and languages. [/quote] Are we reading the same WTF and the same comment? He said he would store the DATE not the month... In the WTF each month has some data associated with it. Like perhaps the number of widgets sold for that month. There is no month name involved. [/quote]

  • FeepingCreature. (unregistered)

    Of course, TRWTF is calling it ImageMagic instead of ImageMagick.

  • hes (unregistered) in reply to tom103

    not a panic, a con game, did you not make $, yen, pounds, bucks, rubles(sic) rubles, pesos, etc. waiting on the next one. was tried again with 2012 but not getting enough traction, especiall with the horrible move leading the charge.

  • Gary (unregistered) in reply to Matt Westwood
    Matt Westwood:
    hoodaticus:
    JiP:
    imgx64:
    TRWTF is the base-12 calendar, obviously. We should move to the decimal system.
    Actually, Napoleon tried something like that once. 10 hour days, 10 minute hours, 10 second minutes. Sadly, the masses rejected this unifyingly brillant concept and it didn't catch on.

    Why don't we actually move to a hexadecimal system?

    For that matter, why don't we move to a unary date system and count the hash marks since Genesis Chapter 1?

    Picoseconds since the Big Bang is probably more appropriate. If we need to know how many that is, just ask god. He's in the next cubicle.

    I love that you can capture picoseconds since the big bang in under 100 bits (and we got Y2K'd because we couldn't fit more than a century's worth of one-day resolution dates into 64 bits).

    We could even manage keeping track of planck times since the big bang with only 200 bits.

    But if we want to keep time until the heat death of the universe, we'll need more bits (but not too many - about 665 or so) to keep ticking off picoseconds as the protons slowly degenerate. Presumably the clock will stop working when entropy is maximized.

  • (cs) in reply to hoodaticus
    hoodaticus:
    boog:
    So March, 2010 would be 1003. It is not clear why it would require 5 characters varchar...
    No, I think it's pretty clear he got his start in C.
    You'd think that would lead to a better, not worse, understanding of varchar. Oh well.
    You'd think so, yes. But I have also run into the type of programmers that believe the STATE column needs to be VARCHAR(3) to allow for null-terminators.
  • (cs) in reply to boog
    boog:
    hoodaticus:
    boog:
    So March, 2010 would be 1003. It is not clear why it would require 5 characters varchar...
    No, I think it's pretty clear he got his start in C.
    You'd think that would lead to a better, not worse, understanding of varchar. Oh well.
    You'd think so, yes. But I have also run into the type of programmers that believe the STATE column needs to be VARCHAR(3) to allow for null-terminators.
    So when you face-palm, do you hit your head, or theirs?

    Just wondering...

  • Rawr (unregistered) in reply to chrismcb

    [quote user="chrismcb"][quote user="Rawr"]

    1. Why are we hitting the database for something as simple as a month? There are very few reasons why we need to hit the database for this. [/quote] You aren't hitting the database for something as simple as a month. You are getting the data stored for a particular month.

    [quote user="Rawr"] 2) Why are we storing months in a database table in the first place? Months are available in the database, and they are available for a multitude of regions and languages. [/quote] Are we reading the same WTF and the same comment? He said he would store the DATE not the month... In the WTF each month has some data associated with it. Like perhaps the number of widgets sold for that month. There is no month name involved. [/quote] [/quote]

    I think you're correct, for some reason the example in the code confused me.

    Not sure how I imagined that one, but here is where I blame it on lack of caffeine, or it being a Monday... to avoid looking like the complete retard I just proved myself to be. Good catch.

  • (cs) in reply to Rawr
    Rawr:
    chrismcb:
    Rawr:
    1) Why are we hitting the database for something as simple as a month? There are very few reasons why we need to hit the database for this.
    You aren't hitting the database for something as simple as a month. You are getting the data stored for a particular month.
    Rawr:
    2) Why are we storing months in a database table in the first place? Months are available in the database, and they are available for a multitude of regions and languages.
    Are we reading the same WTF and the same comment? He said he would store the DATE not the month... In the WTF each month has some data associated with it. Like perhaps the number of widgets sold for that month. There is no month name involved.
    I think you're correct, for some reason the example in the code confused me.

    Not sure how I imagined that one, but here is where I blame it on lack of caffeine, or it being a Monday... to avoid looking like the complete retard I just proved myself to be. Good catch.

    Really? Fuck man, if you're looking like a retard only one day a week, you're leaps and bounds ahead of me...

    BTW - fixed your quote fail, ya retard!

  • lesle (unregistered) in reply to QJo
    QJo:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    Could have been called Godfrey.

    Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.

    The government agency Miguel Orona worked for was first initial, last name. The poor guy was known (true) as morona.

  • (cs) in reply to lesle
    lesle:
    QJo:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    Could have been called Godfrey.

    Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.

    The government agency Miguel Orona worked for was first initial, last name. The poor guy was known (true) as morona.

    I'd hate to have the name Maurice O'Lester...

  • Labias and Genitalia, it's ZUNESIS!!! (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    lesle:
    The government agency Miguel Orona worked for was first initial, last name. The poor guy was known (true) as morona.
    I'd hate to have the name Maurice O'Lester...
    Hey, why not? We could hang out, man! Just two guys bachin'-it-up while your mother's away on her business trip.
  • corwin766 (unregistered) in reply to C-Octothorpe

    [quote user="C-Octothorpe"][quote user="lesle"][quote user="QJo"][quote user="GalacticCowboy"] Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.[/quote]

    The government agency Miguel Orona worked for was first initial, last name. The poor guy was known (true) as morona.[/quote]I'd hate to have the name Maurice O'Lester...[/quote] I was at one place with the rule. Worked with an African American named Alan Ryan.

  • Joe (unregistered) in reply to RichP
    RichP:
    GOD DATE MANGLING!

    That's almost what I would have exclaimed if I had to deal with this code.

    You're pretty sick if you would call that GOOD DATE MANGLING!

    --Joe

  • Herby (unregistered) in reply to Childish
    Childish:
    Actually, I think the Romans meant to have a 10 month calendar. Look at the Latin names:

    September :- sept=7 October :- octo=8 November :- nova=9 December :- deca=10

    The Moon just circles the Earth too many times in a year.

    Actually the old Roman calendar started in March, where the vernal equinox was. This led to "April Fools" who wanted to think that April was the second month after the change!

  • (cs) in reply to FlyboyFred
    FlyboyFred:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    I thought maybe it was GOD Over Djinn.

    No, that's GOD Over Dijon. The King of Mustard.

  • (cs) in reply to C-Octothorpe
    C-Octothorpe:
    boog:
    hoodaticus:
    boog:
    So March, 2010 would be 1003. It is not clear why it would require 5 characters varchar...
    No, I think it's pretty clear he got his start in C.
    You'd think that would lead to a better, not worse, understanding of varchar. Oh well.
    You'd think so, yes. But I have also run into the type of programmers that believe the STATE column needs to be VARCHAR(3) to allow for null-terminators.
    So when you face-palm, do you hit your head, or theirs?

    Just wondering...

    Why would I face-palm when I can laugh in their face?

  • (cs) in reply to QJo
    QJo:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    Could have been called Godfrey.

    Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.

    Ah, I remember a friend from college called Ana. We had a printing system where the first page was always a cover page with your username in big letters on it. It must have been quite embarrassing for her to get the printouts. At least she had a few numbers attached to her username composed of her first name plus initial of her family name starting with "L".

  • Anon (unregistered) in reply to MP79
    MP79:
    this isn't really much of a wtf. I mean, the code simply won't work. Any reasonable test of this will fail. Side bar has seen much better wtf's recently.

    If this site stopped posting stories for any chunk of code where "any reasonable test would fail" there would hardly be any stories left to read...

  • (cs) in reply to QJo

    Seems to fit. When I was in high school, all the computers set up in classrooms, computer labs, etc all had some remote monitoring/control software on them (I forget what it was called). Anyway, the head IT guy would sometimes use it to mess with students he knew, like disabling input from the student machine and sending them messages. When he did this, he would always use the name God. So, I looked up the software he was using, downloaded a free client, and discovered that, surprise surprise, he NEVER SET A PASSWORD. So I did what any student would do: used it to control the IT guys computer and mess with his fantasy football team he had open in a browser (yep, he installed the server side on his pc for some reason). Never call yourself god, you're just making yourself a target.

  • (cs) in reply to No One
    No One:
    Matt Westwood:
    Picoseconds since the Big Bang is probably more appropriate. If we need to know how many that is, just ask god. He's in the next cubicle.
    Don't you mean Planck time since the Big Bang?
    That's the one. Good call. Should have remembered that. Might give us numbers bigger than what you can fit in a smallint, I dunno, can't work it out at the moment, let's use a long, that should be enough. Math is hard. Let's go shopping.
  • (cs) in reply to Anonymous
    Anonymous:
    TOWTF (The other WTF) is that Lori seems to have a problem with using php, javascript and imagemagick to generate graphs. If you want it server side and the company uses php, you use php. If you want the graph to be interactive, javascript is an option, and in order to generate the graph, imagemagick makes as much sense as HTML5.

    You suggesting HTML5 makes no sense? Don't tell my current client, he might believe you and bang goes my contract.

  • Bob (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    Rawr:
    chrismcb:
    Rawr:
    1) Why are we hitting the database for something as simple as a month? There are very few reasons why we need to hit the database for this.
    You aren't hitting the database for something as simple as a month. You are getting the data stored for a particular month.
    Rawr:
    2) Why are we storing months in a database table in the first place? Months are available in the database, and they are available for a multitude of regions and languages.
    Are we reading the same WTF and the same comment? He said he would store the DATE not the month... In the WTF each month has some data associated with it. Like perhaps the number of widgets sold for that month. There is no month name involved.
    I think you're correct, for some reason the example in the code confused me.

    Not sure how I imagined that one, but here is where I blame it on lack of caffeine, or it being a Monday... to avoid looking like the complete retard I just proved myself to be. Good catch.

    Really? Fuck man, if you're looking like a retard only one day a week, you're leaps and bounds ahead of me...

    BTW - fixed your quote fail, ya retard!

    I've told you before and I really don't like to find that I'm having to tell you again. My son was intellectually special, you understand, more-than-averagely deserving of extra special love and affection and care. Here you are, you nasty people, using that horrid word "retard" again. You've managed to reduce me to tears this time. Why can't you have pity on my feelings?

  • (cs) in reply to lesle
    lesle:
    QJo:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    Could have been called Godfrey.

    Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.

    The government agency Miguel Orona worked for was first initial, last name. The poor guy was known (true) as morona.

    A friend of mine had a client called Richard Head. "Oh, just call me Dick," he said, at their first meeting.

  • (cs) in reply to Bob
    Bob:
    I've told you before and I really don't like to find that I'm having to tell you again. My son was intellectually special, you understand, more-than-averagely deserving of extra special love and affection and care. Here you are, you nasty people, using that horrid word "retard" again. You've managed to reduce me to tears this time. Why can't you have pity on my feelings?
    Wait, feelings? You have more than one?! Now THAT'S the real WTF...
  • Anon (unregistered) in reply to Bob
    Bob:
    I've told you before and I really don't like to find that I'm having to tell you again. My son was intellectually special, you understand, more-than-averagely deserving of extra special love and affection and care. Here you are, you nasty people, using that horrid word "retard" again. You've managed to reduce me to tears this time. Why can't you have pity on my feelings?

    Don't be retarded.

  • (cs) in reply to QJo
    QJo:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    Could have been called Godfrey.

    Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.

    These systems can be trouble for Poole G too.

  • moxy (unregistered) in reply to Moxy

    Now I eat humble pie.

  • (cs) in reply to Herby
    Herby:
    Actually the old Roman calendar started in March, where the vernal equinox was. This led to "April Fools" who wanted to think that April was the second month after the change!
    You're right about the Roman calendar; September was the seventh month, counting March as first, etc. The date(s) and reason(s) for All Fools' Day are more complex. (from the Wikipedia article): "In the Middle Ages, New Year's Day was celebrated on March 25 in most European towns. In some areas of France, New Year's was a week-long holiday ending on April 1. Many writers suggest that April Fools originated because those who celebrated on the January 1 made fun of those who celebrated on other dates." http://en.wikipedia.org/wiki/April_Fools%27_Day
  • (cs) in reply to QJo
    QJo:
    GalacticCowboy:
    Obviously, his name was "Gregory Oliver Davis" (or something like that) and they named everything with initials.

    Could have been called Godfrey.

    Then there was the place where our username used to be our first name (or diminutive) concatenated with the first letter or our surname. Yes, Chris T had an attitude problem.

    I can't imagine what he had to be upset about. I bet Takeshi Takeda got way more junk mail.

  • Some guy from some place (unregistered) in reply to tom103
    tom103:
    This year/month representation also doesn't handle dates prior to 2000 (or later than 2099), which is quite unforgivable after the panic caused by Y2K...
    Maybe the 5 characters is so that they can handle dates after 2099...

    Of course, any god would be able to forsee how long his program would last. Perhaps he knew it had a finite life.

  • Jury (unregistered) in reply to Daniel Fountain
    Daniel Fountain:
    Or perhaps if someone is conceited enough to call themself a god they should realise there is ALWAYS something you dont know how to do in any area of IT. No one knows everything.

    Or sometimes some people seem to know nothing.....

    Bullshit! There are plenty of regulars on this site that know everything. I seem them daily!

  • Pjoterffies (unregistered) in reply to Severity One
    Severity One:
    portablejim:
    Is there really a difference when you are selecting 2 of 2 fields? Is it so you don't have to look up somewhere else the fields you are returning? Other reasons?
    You're assuming that the database table structure is immutable and that no DBA or other developer decides to add, say, 100 columns. If you don't need all columns, don't select all columns, because they're all sent over the network and increase the load on the network, the database server and the client application.

    Also, if you do 'select *' and then get rows 1 and 2, and somebody modifies the table structure and inserts a field between what used to be rows 1 and 2, your application ceases functioning. (Pre-empting another common mistake here.)

    'select *' is a sign of laziness. And whilst certain kinds of laziness are good assets for a developer (spending a week to write a program that will save you 10 minutes on each new project that you start), other kinds of laziness are liabilities (doing something the easy way because you couldn't be bothered to do it the proper way, like copy-and-paste code).

    There is a difference between laziness and foresight. Particularly in this context. What does the 10 minute saving achieve? It probably doesn't mean the dev goes home early, but rather that he starts other work 10 minutes sooner.

    Also, for the politically correct: I'm not lazy, I'm just energy efficient.

  • Father Time (unregistered) in reply to JiP
    JiP:
    imgx64:
    TRWTF is the base-12 calendar, obviously. We should move to the decimal system.
    Actually, Napoleon tried something like that once. 10 hour days, 10 minute hours, 10 second minutes. Sadly, the masses rejected this unifyingly brillant concept and it didn't catch on.

    Why don't we actually move to a hexadecimal system?

    24s and 60s are good, because they have many factors 24 has factors 1,2,3,4,6,8,12 60 has factors 1,2,3,4,5,6,10,12,15,20,30,60 1440 (minutes in a day) can (without remainders or decimal places) be divided by 1,2,3,4,5,6,8,9,10,12,15,16,18,20,24,30,32,36,40,45,48,60,72,80,90,96,120,144,160,180,240,288,360,480,720,1440

    So fractions (with low denominator) of an hour are almost always a whole number of minutes, and fractions of a day even more so.
    I'm not sure there is much need to easily find 1/8th of an hour, but I can imagine how halves, thirds, quarters -a and even eighths and ninths will allow accuracy to the second.

    If we wanted simple division by all numbers 1-10 (the only one missing now is 7) we would need to go to 2520 (And which would be difficult to scale - should the factor of 7 be added to minutes or hours?). I think this current system is actually remarkably clever....

    10 is handy because we have learnt to adapt it easily to allow fractions to be represented nicely, but it is not necessarily the best numbering system for all purposes.

  • BrettM (unregistered) in reply to Moxy
    Moxy:
    Once, I was the King of Spain.
    "All kings is mostly rapscallions, as fur as I can make out." -- Huck Finn

    Probably the same is true of gods.

    But me, I was the Prince of Chichester. Pass the cheese dip.

  • Father Time (unregistered) in reply to Hortical
    Hortical:
    Hortical:
    Matt Westwood:
    hoodaticus:
    Why don't we actually move to a hexadecimal system?
    For that matter, why don't we move to a unary date system and count the hash marks since Genesis Chapter 1?
    Picoseconds since the Big Bang is probably more appropriate. If we need to know how many that is, just ask god. He's in the next cubicle.
    The only cubicle next to me is empty. Does this mean I can eat at Mooby's with no worries?
    Oh sure, an invisible god!!!

Leave a comment on “God Date Mangling 101”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article