Cloudflare, DNS, and the Nature of Time
As you probably know by know, Cloudflare had a bit of a DNS issue with the leap second.
TL;DR - Time briefly went backwards somewhere in the code, and everything freaked out. They fixed it. Fast 🎆🎉🎆
Which is an excellent segue about being agile (and Agile, if that is what you do). In particular, that it's not about getting it right (though you should try! Lords yes!), it's what happens when you get it wrong (because you will. A lot. Yes, even you). S**t happens all the time - even on #NewYearsEve. Especially on #NewYearsEve!
Which is as good a time as any to resurrect these old "Time does not behave the way you think it does" posts.
Read them. Part One, and Part Two.
Internalize them.
And as - with certainty - it happens to you again, come back read them Yet Again, and #FacePalm 🤕
🤕 - I have run into, probably, every one of these at least once 🤕🤕
🤕🤕 - Note the "at least"
🎆🎉🎆 - I'd like to believe the below is how it happened
TL;DR - Time briefly went backwards somewhere in the code, and everything freaked out. They fixed it. Fast 🎆🎉🎆
Which is an excellent segue about being agile (and Agile, if that is what you do). In particular, that it's not about getting it right (though you should try! Lords yes!), it's what happens when you get it wrong (because you will. A lot. Yes, even you). S**t happens all the time - even on #NewYearsEve. Especially on #NewYearsEve!
Which is as good a time as any to resurrect these old "Time does not behave the way you think it does" posts.
Read them. Part One, and Part Two.
Internalize them.
And as - with certainty - it happens to you again, come back read them Yet Again, and #FacePalm 🤕
🤕 - I have run into, probably, every one of these at least once 🤕🤕
🤕🤕 - Note the "at least"
🎆🎉🎆 - I'd like to believe the below is how it happened
Comments