|
18 Character Limit posted:Yeah, that happens in the series to some places. Holy poo poo, I knew there was a reason I liked that show as a kid.
|
#
?
Oct 20, 2017 16:36
|
|
|
|
| # ? Jun 6, 2024 09:13 |
|
|
Samizdata posted:I need to get the DVDs and watch that again. I have the DVDs. Such a good show. Well, at least my nostalgia tells me it's a good show.
|
|
#
?
Oct 20, 2017 16:45
|
|
|
chin up everything sucks posted:I have the DVDs. Such a good show. So does mine, so that makes two of us.
|
|
#
?
Oct 20, 2017 18:01
|
|
|
A ticket went out, to a vendor who's product we use to manage board meetings.quote:I did some further testing and believe the issue is related to how time zones are handled.
|
|
#
?
Oct 20, 2017 18:03
|
|
|
I saw an incident come through and couldn't help but think of you guys: Desc: Phones are on fire and smoking. Priority: 2-High
|
|
#
?
Oct 20, 2017 18:38
|
|
|
The Fool posted:A ticket went out, to a vendor who's product we use to manage board meetings. I know that time is a savage and brutal beast in the programming world, but PEER REVIEW YOUR loving CODE YOU SODS.
|
|
#
?
Oct 20, 2017 18:47
|
|
|
The Fool posted:A ticket went out, to a vendor who's product we use to manage board meetings. https://www.youtube.com/watch?v=-5wpm-gesOY
|
|
#
?
Oct 20, 2017 18:52
|
|
|
ChubbyThePhat posted:I know that time is a savage and brutal beast in the programming world, but PEER REVIEW YOUR loving CODE YOU SODS. My brain still hurts as I think about what he must have implemented to arrive at that outcome. UGH. THAT ISN'T HOW THAT WORKS.
|
|
#
?
Oct 20, 2017 19:21
|
|
|
ChubbyThePhat posted:My brain still hurts as I think about what he must have implemented to arrive at that outcome. UGH. THAT ISN'T HOW THAT WORKS. This one is my favorite: quote:If my system time is UTC0 and meeting time is local (UTC-12), the offset is 0. (should be -12) Seriously, if I switch between UTC0 and UTC-12, the displayed time does not change at all.
|
|
#
?
Oct 20, 2017 19:27
|
|
|
It entirely reeks of somebody trying to be way more clever than they actually are. The initial shock has passed and now I'm just laughing at it.
|
|
#
?
Oct 20, 2017 19:30
|
|
|
Collateral Damage posted:Recommend they watch this: I used this exact video to explain why I'm not adding time zone calculations to a report, it should be done at the data gathering/database level using some existing code. And until that happens, my reports will be in UTC, since that's what the data source uses.
|
|
#
?
Oct 20, 2017 19:38
|
|
|
In most cases, (IMO) you should be storing the time in UTC, then doing whatever local time transform you need in the client view. Where my vendors product messes up is that they allow you to specify the timezone of the location of the meeting. As a result, they should be doing something like this: code:I'm probably wrong too, but less wrong than they are.
|
|
#
?
Oct 20, 2017 19:56
|
|
|
No, what you do is use an accepted timezone library/module and use that to do all the heavy lifting. Don't write your own TZ routines is the take away here. https://www.youtube.com/watch?v=-5wpm-gesOY (8:50 is where he says to give up and use someone else code) Proteus Jones fucked around with this message at 20:13 on Oct 20, 2017 |
|
#
?
Oct 20, 2017 20:06
|
|
|
You're the second person to post the same youtube clip, I guess I'll actually watch it.
|
|
#
?
Oct 20, 2017 20:21
|
|
|
The Fool posted:In most cases, (IMO) you should be storing the time in UTC, then doing whatever local time transform you need in the client view. I don't think you're far off from what was actually implemented here. They tried to convert every time to a standard "known value" and adjust the offset from there. They obviously did the math incredibly wrong, on top of the logic doesn't quite work. The correct answer is the same one you've seen already; don't do your own timezones. Use a library that already does this for you.
|
|
#
?
Oct 20, 2017 20:52
|
|
|
ChubbyThePhat posted:I don't think you're far off from what was actually implemented here. They tried to convert every time to a standard "known value" and adjust the offset from there. They obviously did the math incredibly wrong, on top of the logic doesn't quite work. If (($UTCTime -eq 0001) -and ($Offset -eq "+1"){$LocalTime = 0101} ElseIf (($UTCTime -eq 0001) -and ($Offset -eq "+2"){$LocalTime = 0201} ElseIf (($UTCTime -eq 0001) -and ($Offset -eq "+3"){$LocalTime = 0301} ...
|
|
#
?
Oct 20, 2017 21:08
|
|
|
That would have worked much better than the attempt at clever math that was made.
|
|
#
?
Oct 20, 2017 21:10
|
|
|
Judge Schnoopy posted:e; the 40 year old guy before him played WOW all day every day at work and was run out by the horde Intentional or not, well done!
|
|
#
?
Oct 20, 2017 22:11
|
|
|
ChubbyThePhat posted:That would have worked much better than the attempt at clever math that was made. I'm pretty sure I'm missing parenthesis in there, so don't put that into production without testing.
|
|
#
?
Oct 21, 2017 02:19
|
|
|
From 1914:
|
|
#
?
Oct 22, 2017 03:23
|
|
|
re: Timezones. I store the timezone the user prefers with the datetime, then on render I display it with the timezone info next to it so that there are no questions. This was hard learned after some timezone fuckery in the app I write and maintain at work. The key thing I learned was that a datetime needs two consderations: the timezone it was inputted as, and the timezone for what context you are rendering it to. ConfusedUs posted:I used this exact video to explain why I'm not adding time zone calculations to a report, it should be done at the data gathering/database level using some existing code. And until that happens, my reports will be in UTC, since that's what the data source uses. KoRMaK fucked around with this message at 03:48 on Oct 22, 2017 |
|
#
?
Oct 22, 2017 03:46
|
|
|
KoRMaK posted:re: Timezones. I store the timezone the user prefers with the datetime, then on render I display it with the timezone info next to it so that there are no questions. At the time it happened, Tableau either did not have any time-zone-adjustment features or I didn't know about them (and couldn't find any). I wasn't about to start making calculated fields to add/remove hours from the date.
|
|
#
?
Oct 22, 2017 03:48
|
|
|
Dick Trauma posted:From 1914: how do you call them if your phone isn’t working? 
|
|
#
?
Oct 22, 2017 04:21
|
|
|
ConfusedUs posted:At the time it happened, Tableau either did not have any time-zone-adjustment features or I didn't know about them (and couldn't find any). Oh lol, yea that was the right thing to do. Never write your own timezone library, as the video says
|
|
#
?
Oct 22, 2017 04:27
|
|
|
TinTower posted:how do you call them if your phone isn’t working? SHUT UP THATS HOW
|
|
#
?
Oct 22, 2017 05:56
|
|
|
TinTower posted:how do you call them if your phone isn’t working? You might want to start noticing that it says "don't 'hit your phone'" not "don't 'hit someone WITH your phone'...", because we can fix several problems at once that way, smartguy  .
|
|
#
?
Oct 22, 2017 06:01
|
|
|
Today I learned not to name applications after human names. Otherwise get e-mails reporting "Cassandra choking on the load" (direct quote)
|
|
#
?
Oct 22, 2017 15:06
|
|
|
Renegret posted:Today I learned not to name applications after human names. Who's a bad app? Who's a wicked naughty little app?
|
|
#
?
Oct 22, 2017 16:32
|
|
|
Renegret posted:Today I learned not to name applications after human names. The real question was, how many times were you warned about the load before it happened? 
|
|
#
?
Oct 22, 2017 16:50
|
|
|
Renegret posted:Today I learned not to name applications after human names. Does she spit data or ingest it?
|
|
#
?
Oct 22, 2017 21:56
|
|
|
Agrikk posted:Does she spit data or ingest it? It just kinda dribbles out.
|
|
#
?
Oct 22, 2017 22:14
|
|
|
|
|
#
?
Oct 22, 2017 23:09
|
|
|
Methylethylaldehyde posted:It just kinda dribbles out. 
|
|
#
?
Oct 23, 2017 04:42
|
|
|
Dick Trauma posted:From 1914: I am printing this out and putting it on the IT departments door. You wouldn't believe how often people admit they "tried hitting a few times" to make something work.
|
|
#
?
Oct 23, 2017 06:29
|
|
|
Attestant posted:I am printing this out and putting it on the IT departments door. You wouldn't believe how often people admit they "tried hitting a few times" to make something work. percussive maintenance is a thing. https://electronics.stackexchange.com/questions/209010/what-is-the-science-behind-percussive-maintenance
|
|
#
?
Oct 23, 2017 06:52
|
|
|
RFC2324 posted:percussive maintenance is a thing. "Call our complaint department" in response to your phone not working is great advice.
|
|
#
?
Oct 23, 2017 06:59
|
|
|
RFC2324 posted:percussive maintenance is a thing. I remember an old story I heard that when the Army switched over to lead-free solder in a lot of their electronics they actually had a problem where said solder tended to create crystalline fibers that caused shorts. So you ended up with scenarios where any electronics on a piece of equipment that vibrated worked find because those crystals would shake off, but stuff that was used gently would fritz out and short. So you'd have Army technicians fixing their officer's radio by "accidentally" dropping it because they don't want to admit to their officer they fixed the radio by slamming it against the desk.
|
|
#
?
Oct 23, 2017 08:43
|
|
|
Alkydere posted:I remember an old story I heard that when the Army switched over to lead-free solder in a lot of their electronics they actually had a problem where said solder tended to create crystalline fibers that caused shorts. So you ended up with scenarios where any electronics on a piece of equipment that vibrated worked find because those crystals would shake off, but stuff that was used gently would fritz out and short. So you'd have Army technicians fixing their officer's radio by "accidentally" dropping it because they don't want to admit to their officer they fixed the radio by slamming it against the desk. Those are Tin Whiskers, and they're still a pain in the dick to this very day.
|
|
#
?
Oct 23, 2017 10:04
|
|
|
Methylethylaldehyde posted:Those are Tin Whiskers, and they're still a pain in the dick to this very day.
|
|
#
?
Oct 23, 2017 13:32
|
|
|
|
| # ? Jun 6, 2024 09:13 |
|
|
A former customer of mine had to shut down a large video production studio for several days because the mains in the battery backup - generator transfer switch had tin whiskers that were almost in contact with each other. I heard they wanted to get an exception from the state for leaded replacement components, but I don't know if that actually came through.
|
|
#
?
Oct 23, 2017 13:47
|
|
