• 1 Post
  • 119 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle





  • You can prevent downtime by mirroring your container repository and keeping a cold stack in a different cloud service. We wrote an loe, decided the extra maintenance wasn’t worth the effort to plan for provider failures. But then providers only sign contracts if you are in their cloud and you end up doing it anyways.

    Unfortunately most victims aren’t using best practices let alone industry standards. The author definitely learned the wrong lesson though.





  • Fellow 90s kid, my parents were exactly the same. Religious background, fox news constantly, I once didn’t text back within 2 hours and had a neighbor contacted via Facebook knocking on my door in my 30s (to be fair I work on call so it’s atypical). I got lectured at 18 for buying an m rated game in front of them… Police report was a bit much; but I you aren’t alone.

    Side note I would recommend this nostalgic song: high fives - 90s kid anthem by Dr awkward





  • 06:30-02:30 (note the 0!) means 6:30 am to 2:30 am the following day. Anything in pm would be +12 hours. 6:30 pm becomes 18:30; 2:30pm is 14:30. Using this format you want 06:30-14:30 which is 8 hours.

    This format is important because it actually solves the problem you are trying to explain (am/pm). Regularly I need to give EST database timestamps for a PST server cluster while living in another timezone myself and speaking to someone in India which is :30min difference in time zones and trying to account for daylight savings. Removing am/pm just makes it easier to track what happens in different places without looking at the wrong time window. Time math is messy and stupid, be specific by using 24 hours instead of 12

    Edit: I guess no one works in timestamps, keep on being terrible for the rest of us.

    Edit 2: if you don’t understand how time works, reconsider your opinion. Spreading misinformation is damaging