Please note that, for several hours, the above node contained just this:
Go write one. :-D
Now, presumably in response to this original unhelpful reply being downvoted,
sundialsvc4 subsequently heavily edited it, adding
five new paragraphs,
but without indicating he had done so.
This is a violation of long-standing Perl monks
posting etiquette,
as indicated at the Perl Monks FAQ (How do I change/delete my post? and How do I post a question effectively?):
Mark the changed/new content with the word "Update."
Is this a new sundialsvc4 tactic,
to go with previously seen tactics (touched on at Re^2: Maximum down-votes per monk/day and Maximum down-votes per monk/day) namely:
- Not providing code to prove his pet theories.
- Ignoring posts that demonstrate flaws in his technical advice.
- Re-posting the same flawed technical advice over and over, even after it has been shown to be flawed.
- Repeatedly posting the same home-spun wisdoms to questions to which they barely relate.
- Repeatedly opening new discussions on banning anonymous monk and downvotes
- ... while repeatedly claiming he does not mind being downvoted!
- Making unfounded accusations that he is being downvoted by sock-puppet accounts and bots (e.g. here, here, here).
- Not following up on bugs he claims to experience with this site, in particular being repeatedly logged out.
- Posting at length on topics on which he has limited experience or expertise.
- Replying to the wrong post, thus losing context.
- Decorating posts with extravagant typography, stylistic devices, flowery analogies, and unnecessary quotes.
Update: After being criticized for never posting code,
sundialsvc4 appears to be experimenting with a new tactic,
namely posting
extemporaneous code (again again again again again),
pseudocode,
and untested code
and a quasi-Perl sketch with C++ comments.
Update: Wow, on Jun 23 2015, sundialsvc4
actually posted some working code!
And still responding to the wrong post
I see (and again and again and again and again
and again and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again
and again).
And replying with lots of words but little real content.
Update 2017: And, though I thought it impossible, the annoying typography seems to be getting worse: Re: Anonymous Monk comment(s) on questions.
Update: And ignores corrections, re-posting the same guff over and over. For example "Swiss Army knife" - see Re^2: Why did you become a Perl expert (or programmer)?.
Update 2018: Hmmm, looks like sundial has gone incognito:
Experience points over time.
Re: Lots of votes with nowhere to go :-) indicates he had around 13,000 experience points as at May 4 2013.
Re^10: RAM: It isn't free . . . indicates he had 16,251 experience points as at Jan 15 2015.
April 1 2018 16,412 xp,
April 11 2018 16,405 xp,
May 1 2018 16,394 xp,
May 4 2018 16,379 xp,
May 14 2018: 16,361 xp,
May 20 2018 16,359 xp,
May 22 2018 16,361 xp,
Update 2015: Wow, sundialsvc4 has all ten worst nodes of the month!
Worst Nodes of The Month
As of Aug 27, 2015 at 01:48 UTC, Next refresh in 20 hours and 30 mins ±15 min
Update 2017: Done it again on his return.
Worst Nodes of The Month
As of Jun 14, 2017 at 12:36 UTC, Next refresh in 14 hours and 30 mins ±15 min
Worst Nodes of The Month
As of Aug 18, 2017 at 16:28 UTC, Next refresh in 17 hours and 15 mins ±15 min
Worst Nodes of The Year
As of Aug 18, 2017 at 16:28 UTC, Next refresh in 17 hours and 15 mins ±15 min
Update 2018: Finally he has all twenty worst nodes of the year. I believe he is the only one to ever achieve this rare feat.
Worst Nodes of The Week
As of Mar 27, 2018 at 23:44 UTC, Next refresh in 1 hour and 15 mins ±15 min
Worst Nodes of The Month
As of Mar 27, 2018 at 12:21 UTC, Next refresh in 9 hours and 45 mins ±15 min
Worst Nodes of The Year
As of Mar 27, 2018 at 12:21 UTC, Next refresh in 9 hours and 45 mins ±15 min
And again, May 22 2018
Worst Nodes of The Day
As of May 22, 2018 at 20:09 UTC, Next refresh in 15 mins ±15 min
Worst Nodes of The Week
As of May 22, 2018 at 17:30 UTC, Next refresh in 30 mins ±15 min
Worst Nodes of The Month
As of May 22, 2018 at 05:42 UTC, Next refresh in 8 hours and 45 mins ±15 min
Worst Nodes of The Year
As of May 22, 2018 at 13:19 UTC, Next refresh in 16 hours and 15 mins ±15 min