Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Re^3: Automatic downvote

by haukex (Archbishop)
on Mar 31, 2023 at 16:20 UTC ( [id://11151382]=note: print w/replies, xml ) Need Help??


in reply to Re^2: Automatic downvote
in thread Automatic downvote

As a reminder, the context here is that you posted nodes like this one in Seekers of Perl Wisdom. The target audience is people who are new to Perl, learning Perl, etc. We have to assume that anything posted there there can and will be taken by newcomers as real advice (unless explicitly stated otherwise), which is why I, among others, will judge nodes there based on that.

The reason why I like to "reinvent the wheels" is because while doing so, I learn how stuff works.

This is absolutely a great way to learn and I fully encourage this! I would additionally suggest looking into the best practices everyone is recommending and trying to understand why they're being recommended, because you might find some of them useful, even as a hobby programmer. But as I've said several times now, iff you're writing this code just for yourself, your style is fine because TIMTOWTDI. (But you posted your code in SoPW, so the code is not just for yourself.)

Secondly, when I use someone else's code, I have to deal with potential bugs that they left in their code.

This is exactly what you are inflicting on others by posting buggy code!

The difference between a hobby programmer and the hired professional programmer ...

Being both a hobby programmer and a professsional programmer and engineer at the same time, I disagree with most of the generalizations in this paragraph, for example the quickest easiest solution is not always the best solution, at least if you take pride in your work (despite plenty of companies out there discouraging this, of course). But I do understand your explanation of being a hobby programmer, and I do take this into consideration as I write all of this.

I feel it's unfair to judge me based on past code that I wrote earlier.

I agree, and I've posted my really old code. But the node I was talking about is from last week.

Btw some of the things you have linked to that I mentioned earlier turned out to be really bad solutions, and I have since quit using them.

You might want to consider updating your past nodes with that information.

The two-argument open is still something I haven't gotten over yet. I think, I asked someone on here earlier to point me out the security flaw in the program, and all I heard was crickets. Nobody said a word.

The very first link in my post above contains an explanation of a potential security flaw... see also "open" Best Practices.

Like I said, I suggest you post your code in Meditations or Cool Uses for Perl instead. It's perfectly fine to start a post with something like "I saw the post PERL csv files to Excel and it inspired me to write the following code..." - I suspect this will be much more appreciated.

Replies are listed 'Best First'.
Re^4: Automatic downvote
by kcott (Archbishop) on Apr 01, 2023 at 09:12 UTC

    ++ I pretty much agree with everything you've written here except for posting in a different section. Your suggestion of a preface along the lines of "I saw X, it inspired me to write Y" might go some way to mitigating the downvotes of his posts; however, I tend to agree with other responses: bad code and forcing unwanted presentation preferences on others will still garner downvotes.

    Maybe if the preface specifically stated it was code intended to be compatible with 5.004, TinyPerl, or other; and included an exposition of choices such as:

    His posts would probably attract (more) upvotes; although, all of the <font>, bgcolor=, and other annoying and unwanted presentation artifacts would also need to be absent. Other considerations, such as appropriate use of <readmore> or <spoiler> tags, and disuse of inordinately verbose (wall-of-text) sections, would be well-advised.

    — Ken

Re^4: Automatic downvote
by jdporter (Paladin) on Mar 31, 2023 at 19:56 UTC
    I suggest you post your code in Meditations or Cool Uses for Perl instead.

    OK... but posts in those sections are just as game for criticism as any other section. I'd say maybe more so.

      posts in those sections are just as game for criticism as any other section. I'd say maybe more so.

      I'm a bit surprised you think so, and I'm not sure whether I agree... despite there of course not really being a way to measure that. I've usually felt that the criticism in SoPW tends to be harsher for the reasons I named above. But perhaps one of my original suggestions of posting the code as an RFC in Meditations is the best - in any case, my main point of not posting code like that in SoPW still stands.

      Perhaps we need a new "Luke Warm Uses for Perl" section. :) Instead of "Luke Warm" we might try "Quirky" or "Wacky" or "Unorthodox". Suggestions welcome.

      Of the existing sections, posting to Obfuscated code might result in fewer downvotes.

        Perhaps we need a new "Luke Warm Uses for Perl" section. :)

        smiley noted. :-)

        Of the existing sections, posting to Obfuscated code might result in fewer downvotes.

        It will result it lots of downvotes if it's just bad code and not true obfuscation. People have expectations. :-)

        Today's latest and greatest software contains tomorrow's zero day exploits.
        Instead of "Luke Warm" we might try "Quirky" or "Wacky" or "Unorthodox"

        But many unorthodox uses for Perl are just ahead of their time and have yet to become mainstream...

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11151382]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (4)
As of 2024-04-20 00:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found