in reply to How to access results of XML::Simple?

Please always express your question in words.
Saying "it doesn't work" isn't very useful.
Always describe what the code is supposed to do (especially when it doesn't do it).

Also, add

use Data::Dumper; die Dumper $xml;
To your snippet, and hopefully you'll see why it doesn't work (it's cause there is no key in %$xml called gene).


MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: XML::Simple
by sauoq (Abbot) on Dec 18, 2002 at 01:46 UTC

    -- PodMaster

    I wouldn't say anything but I've seen several replies like this from you recently and I've bitten my tounge enough.

    Although I agree that the question was poorly stated, I really think that your tone is offensive and arrogant. Putting your hands on your hips and wagging your finger is no more polite than a poorly asked question and no less a waste to read.

    You are free to skip questions which you can't interpret, you can't answer, or which you feel aren't asked skillfully enough.

    Hubris might be good in the context of being a programmer but it isn't a desirable personality trait. Some, such as the ever quotable MJD¹, excel at what they do to the degree that they can get away with it. I don't think that you have earned that dubious right.

    ¹ Although I've gotten a chuckle from Dominus's rants at the clueless too, I do think it is somewhat of a shame he has managed to set such an example. At least he keeps a sense of humor about it though (mostly.)

    -sauoq
    "My two cents aren't worth a dime.";
    
      I disagree. I felt Podmaster's reply was both helpful and polite. There is no better advice than: "Saying 'it does not work' does not work!"

      --
      Regards,
      Helgi Briem
      helgi AT decode DOT is

      I must also disagree with you, sauoq. Asking for a reasonable explaination of the problem, in words, is not out of the ordinary.

      If I recall correctly, in one of my first posts I was also unhelpful in describing the nature of my problem, and fruiture took me to task for it. (That I flamed him afterwards didn't help either, but live and learn...).

      Since then, I've been highly verbose in describing my problems, and it's been helpful for everyone: I get my answer sooner, other monks don't have to ask questions or make assumptions, and I get more XP. :-P

      I also take exception to your finding PodMaster's tone "arrogant". Are you able to read his mind through the phosphors now? His request seemed very reasonable to me.

      I have a coworker in my office/room/whatever, and he's a nice guy, but he drives me mad -- he can't communicate. Good communication makes things happen. Sometimes I have to tell him to speak up, speak clearly, or re-write an email so I can make sense of what he's saying. He doesn't like it, but he'll be a better worker for it.

      Maybe his future employers will thank me.

      Cheers,
      ibanix

      $ echo '$0 & $0 &' > foo; chmod a+x foo; foo;
        I have a coworker in my office/room/whatever, and he's a nice guy, but he drives me mad -- he can't communicate. Good communication makes things happen. Sometimes I have to tell him to speak up, speak clearly, or re-write an email so I can make sense of what he's saying. He doesn't like it, but he'll be a better worker for it.

        Communication is a two way street, ibanix. Look at it the other way around. Reading or listening and interpretting what someone else says or writes are skills just as important as writing or speaking. You can only ask others to go so far in working around your handicaps in those areas.

        He doesn't like it, but he'll be a better worker for it.

        That, sir, is the height of arrogance. It doesn't even matter if you are right. Stating it is arrogant.

        Maybe his future employers will thank me.

        That is both rude and immature.

        -sauoq
        "My two cents aren't worth a dime.";
        
        A reply falls below the community's threshold of quality. You may see it by logging in.