so the app at dayjob has an internal scheduler, one of the formats for which handles, like, "on the 12th at 8am" tests for it were failing intermittently, in daily CI job only i'm curious if there are any devs out there whose trauma runs deep enough they already know the story
-
Show this thread
-
Replying to @chaosprime
Wait, that's an internal scheduler, of the program, that uses a format like that? Not the display format, but that's how the app tracks it for itself? Am I understanding this right or is my reading comprehension broke again
1 reply 0 retweets 3 likes -
Replying to @DoremiRenko
you are understanding it right, that is how the specification of when a job will be run by the scheduler is made
2 replies 0 retweets 2 likes -
Replying to @chaosprime @DoremiRenko
think of it as, like, somebody wanted cron, but readable didn't want to have to remember what a bunch of numbers in different positions meant
2 replies 0 retweets 3 likes -
Replying to @chaosprime @DoremiRenko
this is easily the dumbest shit I've ever read, thanks
2 replies 0 retweets 2 likes -
Replying to @WanderingArbor @DoremiRenko
i mean, i could tell you about the global utility function 𝚞𝚝_𝚏𝚊𝚕𝚜𝚎() whose purpose in life is to return the value 𝚏𝚊𝚕𝚜𝚎 if that would help
1 reply 0 retweets 2 likes -
Replying to @chaosprime @WanderingArbor
Wait what the fuck When would you ever need that
1 reply 0 retweets 2 likes -
Replying to @DoremiRenko @WanderingArbor
oh well let's say you had a data validation architecture whose validation models had 1) a delegate function to do the validation 2) an error message for if it fails, but you weren't using it the way it was designed because you wanted to check the condition outside the delegate
1 reply 0 retweets 2 likes -
because of *waving hands* there being a bunch of stuff you'd want to load sometimes but not other times to do the check and it would all be too hard inside the delegate or something. but then you still want the data validation architecture to produce results in its style
1 reply 0 retweets 2 likes
so then you *might*, or rather *one* might because certainly let us not personalize this, add a validation condition that has the error message you want and a delegate that's always false because you're only applying it if you already know it's failed
-
-
and then you might want a nice handy 𝚞𝚝_𝚏𝚊𝚕𝚜𝚎() function because you were writing all this way the fuck before the language it was written in got anything so fancy as dynamic delegates, and also you're too lazy to just make the fucking delegate handler handle 𝚏𝚊𝚕𝚜𝚎
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.