• (cs)

    It must really suck to have to go through 20 GB of logs.

    Choosing an editor for that is like picking a paddle once you're already down S*** Creek.

  • (cs)

    Apart from the obvious "TRWTF is Spring" and "TRWTF is malformed XML", TRRWTF (the really real WTF) is busy waiting. Is there no blocking read?

  • (cs) in reply to lucidfox
    lucidfox:
    Apart from the obvious "TRWTF is Spring" and "TRWTF is malformed XML", TRRWTF (the really real WTF) is busy waiting. Is there no blocking read?
    Yes, there is!
  • (cs) in reply to lucidfox
    lucidfox:
    Apart from the obvious "TRWTF is Spring" and "TRWTF is malformed XML", TRRWTF (the really real WTF) is busy waiting. Is there no blocking read?
    “It didn't work last time. Let's try again! Right now!” <sigh…>

    (Spring isn't TRWTF; it's just doing what anyone truly competent would choose to do with a scripting language instead. The widespread misunderstanding of what Spring is and isn't is a WTF, but not one that is the subject of the article.)

  • Barf 4Eva (unregistered)

    "There was no reconnect code. No progressive delays between dumping identical log errors. No email to support-lists saying "Bad thing happened!"

    Just a lone comment in the source code from the Architect's Architect saying: "Trust me!" "

    At the beginning of the article, thousands of exceptions were being thrown, in line with the logging of the error from the catch statement. So, no, it wasn't just a comment that they were reliant on here. Although bad as it is, it could have been worse...

    catch { //trust me! }

  • (cs)

    I was hoping to see the phrase "Trust me, I know what I'm doing", possibly followed by "Sledge, you can't solve everything with an infinite loop!"

  • Vance (unregistered) in reply to Anon
    Anon:
    Michael:
    Often someone's first (and most egregious) mistake is assuming that they don't make mistakes...

    What are these "mistakes" of which you speak? I might like to try making one once.

    Well, it's kind of like a stnank.

  • Aninnymouse (unregistered) in reply to Calli Arcale
    Calli Arcale:
    Tip: "Trust Me" should only be trusted if it is followed with "I'm the Doctor." Unless you're a Dalek.

    Or if it's followed by "I'm a rat."

  • lmpeters (unregistered) in reply to Jazz

    The worst use of XML I've ever seen was in the LDAP plug-in for Apache Jetspeed (a Java portal server) about five years ago. The plug-in itself was a Java class whose constructor took 36 arguments (yes, 36!), and the way you'd configure it was to write an XML file that specified each argument to that constructor by position. I think it looked something like:

    <param pos="1" value="abc"/> <param pos="2" value="123"/> ... <param pos="36" value="are we done yet?"/>

    I kind of suspect it was written by someone at a certain company that makes its own closed-source Java-based portal server, in order to make the open-source alternative look bad.

  • someone (unregistered) in reply to Tzafrir Cohen
    Tzafrir Cohen:
    Naturally you could use more to browse it. It uses a constant amount of memory.

    Less is more than more. It has a more usable text search capability (not just simple search forward). It uses more memory. But it will also use O(1) memory (unless you pipe data into it).

    There are also some editors that will work this way. Vim, sadly, is not one of them. I believe that nvi is, though. But my initial test shows that (unlike less) it needs to scan the whole file before providing the initial display (it uses a temporary file?)

    I think it scans the file to get line numbers. (like less)

    You can press ctrl+c after opening and it will stop, and just show the file

  • Lester Moore (unregistered) in reply to Naranek
    Naranek:
    Kasper:
    Dan Mercer:
    Do people not use "less" and "more" anymore?
    There are people who use less or more, but probably not both at the same time.

    I use less all the time.

    I also use less more or less all the time, and more much less.
    When I was in charge, the more I used less the less I used more. But now I'm buried in the Boot Hill Cemetery in Tombstone, Arizona: Here lies Lester Moore Four slugs from a .44 No Les No Moore.

  • Bill C. (unregistered)
    snoofle:
    Also, due to the system it was to replace being notoriously buggy and unreliable, this system had to be bullet proof. It simply could not go down.
    That sounds like a job for the president's daughter, not an intern.
  • Zog (unregistered)

    Another ****-hot architect with no knowledge of the basics of how priority queues work....I bet there are race conditions and all sorts of oddities there that our "architect" couldn't even think of..

    ...trust me!

  • Happy (unregistered) in reply to michael

    Don't you know? MQ NEVER loses messages!

  • (cs) in reply to Drake
    Drake:
    "What if the president's daughter is sick and the server is overheating?"

    "Trust me!"

    What if the president's daughter's sick is overheating?

  • (cs)

    TRWTF are people in IT who use editors to read log files. There are tools, more or less, suited to that problem.

    TRRWTF is busy polling empty queues without ever sleeping, wasting CPU power for nothing.

    TRRRWTF is Active MQ.

    TRRRRWTF is the JMS spec, which does describe a message priority, but does not really enforce implementors to support it: "(...) does not have to deliver messages in exact order of priority."

    How lame is that? And of course JMS implementors fuck that up, leading to such "separate queue for high priority messages"-WTFs as described in the article.

  • furiant (unregistered)

    So there was this software and it had a bug. And there wasn't an ironic comment in the code, we just added that for effect. Funny huh? A real WTF.

  • HerrOttoFlick (unregistered) in reply to Steve The Cynic
    Steve The Cynic:
    Bob:
    The real wtf is opening logs in an editor. Saying that, I open 20meg files in vim all the time.
    That's cool. Read more carefully, though. A 20 *gig* file might challenge it a little more.

    This is why Bram in his wisdom gave us the -n flag.

    If you cant remember that, "more" or "less" would also have allowed our intrepid bug fixer to view the file just fine. It does take a long time to read a full 20GB of logs though.

  • HerrOttoFlick (unregistered) in reply to Bill C.
    Bill C.:
    snoofle:
    Also, due to the system it was to replace being notoriously buggy and unreliable, this system had to be bullet proof. It simply could not go down.
    That sounds like a job for the president's daughter, not an intern.

    The Vice President's daughter does not go down. Trust me.

  • English Man (unregistered)

    The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.

    -- Douglas Adams

  • jay (unregistered) in reply to Anon
    Anon:
    Michael:
    Often someone's first (and most egregious) mistake is assuming that they don't make mistakes...

    What are these "mistakes" of which you speak? I might like to try making one once.

    I thought I had made a mistake once. But then it turned out that I was mistaken.

  • jay (unregistered) in reply to Kasper
    Kasper:
    Dan Mercer:
    -- Opening a 20 GB file is no problem with vim. -- Or emacs.

    Do people not use "less" and "more" anymore?

    There are people who use less or more, but probably not both at the same time.

    I use less all the time.

    If you are opening log files in an editor, you are doing it wrong. Log files are not supposed to be edited, so why would you use an editor?

    Umm, because that's the easiest way to read a text file?

    Just because it's called an "editor" doesn't mean that it can only be used to edit. Just because a language is called "Java" doesn't mean you can only use it in Indonesia.

  • (cs) in reply to no laughing matter
    no laughing matter:
    TRWTF are people in IT who use editors to read log files. There are tools, more or less, suited to that problem.

    TRRWTF is busy polling empty queues without ever sleeping, wasting CPU power for nothing.

    TRRRWTF is Active MQ.

    TRRRRWTF is the JMS spec, which does describe a message priority, but does not really enforce implementors to support it: "(...) does not have to deliver messages in exact order of priority."

    How lame is that? And of course JMS implementors fuck that up, leading to such "separate queue for high priority messages"-WTFs as described in the article.

    Good troling effort! I bite.

  • qbolec (unregistered)

    I think it would be fun, to see how you guys make this peace of code correct. In particular the exception handling part.

  • Gunslinger (unregistered) in reply to veniam
    veniam:
    Hidden comments in the article make me smile :D

    Hidden comments in the article make me ill and angry.

  • Gunslinger (unregistered) in reply to DCRoss
    DCRoss:
    I was hoping to see the phrase "Trust me, I know what I'm doing", possibly followed by "Sledge, you can't solve everything with an infinite loop!"

    Excellent, Smithers. Excellent.

  • ZoomST (unregistered) in reply to HerrOttoFlick
    HerrOttoFlick:
    Bill C.:
    snoofle:
    Also, due to the system it was to replace being notoriously buggy and unreliable, this system had to be bullet proof. It simply could not go down.
    That sounds like a job for the president's daughter, not an intern.
    The Vice President's daughter does not go down. Trust me.
    She doesn't go down, but she is really overheating.
  • (cs) in reply to jay
    jay:
    Umm, because that's the easiest way to read a text file?
    In what way is it easier than less or more?
    jay:
    Just because it's called an "editor" doesn't mean that it can only be used to edit. Just because a language is called "Java" doesn't mean you can only use it in Indonesia.
    Well, news for you: you can't!

    The official language there is the Indonesion language, sometimes called "Bahasa" by English speakers, though this literally just means "language".

  • Norman Diamond (unregistered) in reply to no laughing matter
    no laughing matter:
    jay:
    Just because it's called an "editor" doesn't mean that it can only be used to edit. Just because a language is called "Java" doesn't mean you can only use it in Indonesia.
    Well, news for you: you can't!

    The official language there is the Indonesion language, sometimes called "Bahasa" by English speakers, though this literally just means "language".

    Bahasa Indonesia is pretty closely related to bahasa Java and bahasa Malay. You can speak it on other islands or countries. For example find a web site to translate the Indonesian word "air" to English.
  • eric bloedow (unregistered)

    this is really silly, but it sort of fits: https://www.youtube.com/watch?v=6ShF3WG1nDg

Leave a comment on “Trust Me”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article