in reply to Re^3: 20 most important Perl Best Practices
in thread 20 most important Perl Best Practices

I copied them from "various sources" which I found on this page. So, these aren't entirely my own rules.

It'd be good if you listed your primary sources while identifying original coding rules that you invented ... I think it's safe to say you invented these two :-)

I'd forgotten I'd already compiled Coding Standards References -- there's certainly no shortage of opinions and references on this topic.

👁️🍾👍🦟
  • Comment on Re^4: 20 most important Perl Best Practices

Replies are listed 'Best First'.
Re^5: 20 most important Perl Best Practices
by jdporter (Paladin) on May 03, 2024 at 13:02 UTC

    Oh, come on. It's not like 11-23 (and half of 24) are your personal inventions. The only thing harangzsolt33 needs to do is rephrase, so that he's not literally plagiarizing.

      The only thing harangzsolt33 needs to do is rephrase, so that he's not literally plagiarizing

      Just to clarify, I was not personally offended by plagiarism in harangzsolt33's reply. Agreeing with LanX, I just feel it's much better to create a link to the original: less work for the poster and more useful to others, allowing them to consult the original sources for themselves.

      To illustrate, I wrongly assumed that "Don't do stupid things" and "Think about what you write" were inventions of harangzsolt33 ... until he replied that they'd been copied from this reply. Regardless of who suggested them, I would argue against including these two in any coding standard I was involved in. :-)

      Update: Perhaps the reason harangzsolt33 is so reluctant to create links to PM nodes is simply that he doesn't know how to! Super-searching for "[id://" in nodes written by harangzsolt33 produced just two hits (Re^3: How to portably stop processes? and Re^4: Automatic downvote), both of which contain "Athanasius fixed link" updates! Despite being told repeatedly to not create links to perlmonks.com (and being shown how to link properly by Athanasius and others) harangzsolt33 has never created an approved "[id://" link to a Perl Monks node.

      👁️🍾👍🦟
      Well a compilation is already a creative act on it's own and works as an ensemble.

      Especially if the wording it consistent, avoiding repetitions and is clear in terminology. °

      As an example:

      If I wrote a Perl tutorial, and occasionally copied a line verbatim from the perldocs without referencing individually, this might be OK. ³

      But if I literally copied >50% without any reference, this wouldn't really qualify as a tutorial... ²

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery

      °) I could tell a story or two about a neighboring university were the math classes for anthropologists are taught by biologists and the students are left to belief it's their fault if the lessons made no sense.

      ²) if I wrote "you shall not murder", I wouldn't really bother citing the accurate passages from the Quran, Bible, Tanakh or Code of Hammurabi. But if I copied a whole passage verbatim, the source should be stated.

      ³) Me, I would personally take care to mention somewhere to the end that small passages were taken from perldoc and thank the authors.

Re^5: 20 most important Perl Best Practices
by harangzsolt33 (Deacon) on May 03, 2024 at 11:43 UTC
    I think, moritz wrote those two. I just literally copied the entire page what I could find here, and I erased and changed it to my taste. Erix mentioned Abigail's guidelines. I copied those too.

    Again, I did not write these rules. I just merged them into a single list, and I did not create this list with the intention that others should adopt these rules or they should follow them. I just simply organized the list for myself. It's a pretty good list. I think, I could find more rules like this if I did a Google search, but I didn't do that.

      The easiest way to shorten this discussion is to be so kind to edit your original post and to add the missing information.

      And here is why:

        When do you need to cite sources?

        Citations are required in all types of academic¹ texts. They are needed for several reasons:

        • To avoid plagiarism by indicating when you’re taking information from another source
        • To give proper credit to the author of that source
        • To allow the reader to consult your sources for themselves]
      On a Meta level, please note that I referenced from where I copied that advice, because...

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery

      ¹) and yes this is strictly speaking not an academy, but monasteries predated universities as centers of wisdom for many centuries.

        Okay, I will do that.