Re^10: Problems with Newest Nodes

I also agree. As i said, it looks to be a relatively easy change compared to all the other stuff that needs improvement (with somewhat smaller consequences in case i mess up) . That's why i was thinking of starting with this one.

perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'

Comment on Re^10: Problems with Newest Nodes Download Code

Replies are listed 'Best First'.
Re^11: Problems with Newest Nodes (KISS) by LanX (Saint) on Jun 16, 2021 at 12:04 UTC
Training is fine, but if I were a god I wouldn't approve bigger changes by a newbie. You have to keep in mind that there might be plenty of inter-dependence. Status quo is that `Show nodes created within the [1] past days [submit]` is shown after "Clearing the last checked time". My suggestion, add a radio to safe the election permanently `Show nodes created within the [1] past days [submit] o adjust last checked` Even this minor change could potentially lead to problems elsewhere, but I doubt anything bigger would be approved. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l] [select]
Re^12: Problems with Newest Nodes (KISS) by jdporter (Paladin) on Jun 16, 2021 at 15:10 UTC
That being said, I would like to see the most ambitious change a pmdevil - regardless of experience level - could propose. I'd rather say: "This bit and this bit are probably too much, in terms of risk; maybe scale it back a bit." But mainly I'd like to see a written plan - a description of the overall change - not just a set of patches and have to figure out myself how they work together. To all pmdevils: Please post under pmdev (and don't forget to change the title appropriately) when you want to propose something non-trivial. Thanks! I reckon we are the only monastery ever to have a dungeon staffed with 16,000 zombies.	[reply]