I'm proposing that DST is an awkward solution to the problem. You're suggesting that we should use the awkward solution and then also stack another solution on top. Why not cut out the extra step?

> Uncle Steve is zero hours ahead.

Uncle Steve is the same number of hours ahead that he has always been, and that's a thing that could be looked up just as easily as finding his time zone. I think the author is greatly exaggerating the degree to which time zones solve any of the problems mentioned. Uncle Steve might be on a different sleep schedule from me, regardless of whether or not he's in a different time zone.

Days of the week definitely become interesting in a global UTC system, but noon used to literally mean "the sun is at it's highest point". I suspect that people would grumble for a year or two and then forget that another system ever existed.

Well, I'm not one of those people. I like waking up with the sun and driving to work in the daylight. The idea that DST solves anything absolutely blows my mind. If you want the ability to start your work day earlier and end it earlier, that seems like a worker protection bill that needs to be passed. DST is the kludgiest kludge that ever kludged.

Well, find and sed have modern "fd" and "sd" alternatives. Naming it "gt" allows you to claim that your version save 33% compared to typing "git".

This is news to me. What motivates you to reach for an S3-backed queue versus SQS?