re: Friends Don't Let Friends Look Dead On The Internet VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Even though it’s completely irrational, my thought process for having it be hardcoded is because if we only have to change it once a year, why re-c...
 

Just want to loop @rhymes in on your response πŸ˜„

 

I'd definitely see the hardcoded date as legacy code, if not now, someday. May as well merge the Time.current.year PR.

Is the compute time of recalculating it over and over again more or less burdensome than receiving multiple PRs and spending the time to address each of them – including closing five (or more next year!) of them?

If you answer that I think you'll have a good reason to either merge or close the Time.current.year PR πŸ€—

Abhaha I agree with you, let's keep it hard-coded or put it dynamic but in a partial, cached until 2019 ends πŸ€”

I actually quite enjoy this odd throwback ritual, but acknowledging that in pure software/productivity terms it should be computed. Merged a PR that does that.

Since we're eyeing a future where people can stand up their own version of our open source platform community, hardcoded dates will eventually be bad legacy code.

Since we're hoping that future happens at some point in 2019, makes sense to go computed now. πŸ˜‚

code of conduct - report abuse