I think the OP was perhaps making a learned observation.

Someone who does c, and sees that code that supposedly came from a friend "who knows" what he's doing- maybe that person would look at it and be asking more questions then the original ones. In fact, a programmer would possibly find it quicker to lookup those answers and quickly learn some regex common sense - then to try to get another human being's attention about it- that early on in the game.

Especially c, c is not "easier" then perl. Saying you're a programmer carries some punch- (and a c programmer.. c is some serious stuff). I try to take it to mean one of two things, either you're not a programmer, or you're a hard veteran. Personally I am not a coder, It's like being a marine in that movie Jughead- getting branded.. anyway.

Personally -I just code. I write some software when I can't find an already existing solution for the problem.

Anyway, the OP came here I think with good intentions, maybe to share some laughs- etc- and it may not be everyone's cup of tea how he does it.

Personally I have been scolded and flat out told "you don't know what you're talking about" by my best teachers in all fields of life. Sometimes you need that- before your mind goes into outer space.

And yes... He wasn't the most explanatory- but he was helpful. I think the conversation did leave it open if the "c programmer" was really a programmer. And if you're gonna learn, to help your teacher you have to tell them what you don't know. Dude was obviously trying to be helpful until he realized that the "c coder" was not being very honest about what he did and did not know.

If the c guy *was* a "programmer", then the way you would go about helping them is different then how you would go about helping them if they are not! So- he needs to ask quick and dirty- "are you a programmer really?"

That's one way of looking at it.

In reply to Re^2: A conversation with a C programmer by leocharre
in thread A conversation with a C programmer by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.