• s (unregistered)

    yes!

  • The Sussman (unregistered)

    Read SICP.

  • Konstantin Guryanov (unregistered)

    Yeah. KillTheChildren is awesome. However a friend of mine has a favorite functionnam ehe uses in many projects he supports. The name is KillKenny. It usually dows something similar to the KillTheChidren in this example.

  • Not Wtf (unregistered)

    BOR-ING

  • glassx (unregistered)

    The GUID idea is more common than we think.

  • Vollhorst (unregistered)

    yawn

  • ha (unregistered)

    I have used phrases about killing the children a few times while solving mathematical problems in graph theory about trees. I stopped do so when my friend noticed that we are talking quite loudly about this on the street and others can hear us.

  • (cs) in reply to ha
    ha:
    I have used phrases about killing the children a few times while solving mathematical problems in graph theory about trees. I stopped do so when my friend noticed that we are talking quite loudly about this on the street and others can hear us.

    Why?

  • xorsyst (unregistered)

    Try getting new GUIDs using SQL server 2000 - they will be that close together. It uses the MAC address followed by the timestamp (or something like that).

  • (cs)

    TRWTF is that the GIDs are not U.

  • oldtimer (unregistered)

    These are not GUIDs! GUIDs are hexadecimal and do not contain Q, O, T etc.

  • augue (unregistered) in reply to Konstantin Guryanov
    Konstantin Guryanov:
    Yeah. KillTheChildren is awesome. However a friend of mine has a favorite functionnam ehe uses in many projects he supports. The name is KillKenny. It usually dows something similar to the KillTheChidren in this example.
    When you run the KillKenny function does it throw a non-blocking exception with the message of "You bastard!" ???
  • (cs) in reply to Not Wtf
    Not Wtf:
    BOR-ING

    MOR-ON.

    Go away.

  • Daniel Von Fange (unregistered) in reply to xorsyst

    Yes, that's totally normal. Version 1 GUID's are basically HASH(MAC address) + timestamp, so if you generate a bunch at once, they look really close together. This also means that you can look at a GUI'd and find out when it was created.

  • Simon (unregistered)

    I don't think the loop inside KillTheChildren actually does anything, since objIntegrationAccount is just a local variable (i.e., a copy of the reference inside the enumeration)...?

  • (cs)

    brillant!

  • Someone (unregistered)

    Back in school, we had a big real world project to build from scratch in the last year. The students that graduated the year before mine had to build something about babies birth management... you guess it, to remove a baby from a list, they asked for confirmation with a message which went something like that : "Do you really want to kill the baby?". When the clients (elderly women) tried the system, they kind of started freaking :P

  • (cs) in reply to Daniel Von Fange
    Daniel Von Fange:
    Yes, that's totally normal. Version 1 GUID's are basically HASH(MAC address) + timestamp, so if you generate a bunch at once, they look really close together. This also means that you can look at a GUI'd and find out when it was created.

    Yes, but how do you explain the non-hex characters at the end of these so-called "GUID"s?

  • Vroomfundel (unregistered) in reply to Daniel Von Fange
    Daniel Von Fange:
    This also means that you can look at a GUI'd and find out when it was created.

    I'm not sure if this is exactly the way hashing works.

  • Benjamin (unregistered)

    I dunno, I think I'd be willing to risk my sanity to see those extra 25 levels of indentation in all their glory.

  • Daniel Von Fange (unregistered) in reply to Vroomfundel

    The timestamp isn't hashed - only the Mac address.

  • London Contractor Mart (unregistered) in reply to oldtimer
    oldtimer:
    These are not GUIDs! GUIDs are hexadecimal and do not contain Q, O, T etc.

    First thing I spotted too!! Thought i was insane but did just look on GuidGen as to be honest I don't pay attention to the contents of my guids!

    I think they have created their own Hex-a-betic guids! I guess they are a bit like alpha-spaghettis (the well known hybrid of the alphabet and that famous Italian dish, Spaghetti)

    Captcha: acsi - which is a bit like the ASCII version of Hex-a-betic!

  • Hehe (unregistered)

    If you think a function name like KillAllChildren is pathetic, look in any photography forum where portrait photography is discussed. You'll find threads with titles: "How do I shoot babies?", "I want to shoot my children", ... these posts mean "photograph" whenever they write "shoot". It still makes me sick when I read such head lines but people in these forums rarely have an issue with this ..

  • Karl von L. (unregistered) in reply to oldtimer
    oldtimer:
    These are not GUIDs! GUIDs are hexadecimal and do not contain Q, O, T etc.

    That's what makes these ones globally unique, duh.

  • Addison (unregistered)

    KillTheChildren? Pshaw!

    I wrote a function last week called "GetOwnedByData()". I did wind up renaming it though.

  • (cs) in reply to augue
    augue:
    Konstantin Guryanov:
    Yeah. KillTheChildren is awesome. However a friend of mine has a favorite functionnam ehe uses in many projects he supports. The name is KillKenny. It usually dows something similar to the KillTheChidren in this example.
    When you run the KillKenny function does it throw a non-blocking exception with the message of "You bastard!" ???
    throw new Exception("You bastard!");
  • VB6 Coder (unregistered) in reply to Simon
    Simon:
    I don't think the loop inside KillTheChildren actually does anything, since objIntegrationAccount is just a local variable (i.e., a copy of the reference inside the enumeration)...?

    I Agree, surely its just creating and destroying references to objects and not actually doing anything.

    The children live!

  • Jim (unregistered) in reply to oldtimer
    oldtimer:
    These are not GUIDs! GUIDs are hexadecimal and do not contain Q, O, T etc.

    And we must abide by your ID conventions because?

  • (cs)

    Either they're using a heavy load of global variables or this is a huge class.

    Look, 10 methods are called without any arguments passed in.

  • (cs) in reply to Jim
    Jim:
    oldtimer:
    These are not GUIDs! GUIDs are hexadecimal and do not contain Q, O, T etc.
    And we must abide by your ID conventions because?
    Because they're Globally Unique ID conventions. If everyone did their own thing, then the conventions might not be GU...
  • (cs) 
    if Born then
   if LivedThroughYear(1) then
      if (LivedThroughYear(2) then
         ...
         if LivedThroughYear(90) then
            kill(Me)
         end if
      end if
   end if
end if
  • Jim (not the dumb Jim) (unregistered) in reply to Jim

    Because GUIDs are a standard and there are many functions that parse GUIDs that will barf on these.

    Or were you simply being facetious?

  • (cs) in reply to xorsyst
    xorsyst:
    Try getting new GUIDs using SQL server 2000 - they will be that close together. It uses the MAC address followed by the timestamp (or something like that).
    Maybe you should actually test your theories before posting them.
  • Not Wtf (unregistered)

    These stories are pants.

  • (cs) in reply to Aaron
    Aaron:
    Maybe you should actually test your theories before posting them.
    That has happened before, but it didn't catch on.
  • APH (unregistered)

    I remember my Operating Systems instructor was always careful when he spoke about Unix. "Forking Children" was a particularly difficult subject.

  • Steve (unregistered) in reply to Konstantin Guryanov
    Konstantin Guryanov:
    Yeah. KillTheChildren is awesome. However a friend of mine has a favorite functionnam ehe uses in many projects he supports. The name is KillKenny.
    Does it have a return value of three cats?
  • Sakkie (unregistered)

    TRWTF is that the "GUIDs" have letters higher in the alphabet than F at the end - methinks those "GUIDs" were handwritten

  • Jim T (unregistered)

    KillTheChildren? Minor league stuff.

    A section of my code as a DestroyAllOrphans method.

    And no, I'm not kidding. I'm quite proud of that method name.

  • Bob (unregistered) in reply to dkf
    dkf:
    Jim:
    oldtimer:
    These are not GUIDs! GUIDs are hexadecimal and do not contain Q, O, T etc.
    And we must abide by your ID conventions because?
    Because they're Globally Unique ID conventions. If everyone did their own thing, then the conventions might not be GU...
    You and your inside-the-box thinking is what makes innovation stagnate!

    I use a GUID that is a hash of my SSN + timestamp / pi-1. This way I always know that I generated them and they can be used to measure the curvature of myself in any space-time. I also salt them twice.

  • Fra Diavolo (unregistered)

    What really mystify me is that GUID 1 and 7 are the same...

    Shouldn't it be a Key??

  • Yazeran (unregistered) in reply to Fra Diavolo
    Fra Diavolo:
    What really mystify me is that GUID 1 and 7 are the same...

    Shouldn't it be a Key??

    Yea I noticed that too.. makes them not quite so unique eh? :-)

    Yours Yazeran.

    Plan: To go to Mars one day with a hammer.

  • (cs) in reply to ha
    ha:
    I have used phrases about killing the children a few times while solving mathematical problems in graph theory about trees. I stopped do so when my friend noticed that we are talking quite loudly about this on the street and others can hear us.
    No, you should definitely continue this. It will help to keep punk ass kids in check if they ever cross your path!
  • (cs) in reply to Bob
    Bob:
    You and your inside-the-box thinking is what makes innovation stagnate!

    I use a GUID that is a hash of my SSN + timestamp / pi-1. This way I always know that I generated them and they can be used to measure the curvature of myself in any space-time. I also salt them twice.

    Do you pepper them too?

  • Mike Dimmick (unregistered) in reply to Aaron
    Aaron:
    xorsyst:
    Try getting new GUIDs using SQL server 2000 - they will be that close together. It uses the MAC address followed by the timestamp (or something like that).
    Maybe you should actually test your theories before posting them.

    Up until Windows 2000, the UuidCreate API used the GUID v1 as specified in RFC 4122. That has a timestamp and uses one of the computer's network card's MAC address. There were privacy concerns surrounding the use of this MAC address. From Windows 2000 onward they changed to use the random number generation system (version 4 GUID) in section 4.4. The old algorithm is still available by calling UuidCreateSequential.

    Perhaps xorsyst is running SQL Server 2000 on NT 4.0?

  • Richard (unregistered) in reply to ha
    ha:
    I have used phrases about killing the children a few times while solving mathematical problems in graph theory about trees. I stopped do so when my friend noticed that we are talking quite loudly about this on the street and others can hear us.
    We had a process in our logistics product, years ago, that was called "Batch order maintenance." The second part of it became "Batch Order Maintenance - B" or "The Bomb."

    Tons of fun until our CEO got detained in an airport (pre 9/11) for discussing it over the phone, and one of our services guys left a voicemail on an old woman's phone (mis-dialed and skipped the outgoing message) about "... getting the bomb queued up to go in Orlando." Actually brought us a visit from the FBI. After that, we all agreed to stop using the term.

    Still makes me chuckle, though.

    Captcha: laoreet

  • Ciaran McNulty (unregistered)

    These definitely aren't properly-generated GUIDs. What tips you off is the third group starts with a 4. In GUIDs that digit indicates the UUID version being used.

    Version 4 GUIDs are meant to be generated using random numbers (not MAC addresses etc. like previous comments have indicated) so the odds of them being that close together are indeed astronomical.

    The real WTF is why someone would make up their own alphanumeric IDs and then format them the same as GUIDs (and not keep them unique).

  • Irish I weren't drunk (unregistered) in reply to Konstantin Guryanov
    Konstantin Guryanov:
    Yeah. KillTheChildren is awesome. However a friend of mine has a favorite functionnam ehe uses in many projects he supports. The name is KillKenny. It usually dows something similar to the KillTheChidren in this example.

    I use the function of Kilkenny in plenty of my personal projects too.

  • Dave G. (unregistered)

    A function named KillKenny is probably better than a function named RootRachelle.

  • drach (unregistered) in reply to Yazeran
    Yazeran:
    Fra Diavolo:
    What really mystify me is that GUID 1 and 7 are the same...

    Shouldn't it be a Key??

    Yea I noticed that too.. makes them not quite so unique eh? :-)

    Yours Yazeran.

    The saddest part to me is seeing just how far down I had to read to find someone else spotted it also. Perhaps these are records related to employees from some other table besides the master employee lookup table?

Leave a comment on “One In 3.4*10^38”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article