Users And Me: The Production Firefighter

Content It's a time zone change on December 31st in shanghal. See this pace for details of 1927 11860 in Shanghai. Basically at midnight at the end of 1927, the clocks went back 5 minutes and 52 seconds. So "1927-12-31 23:54:08" actually happened twice, and it looks like Java is parsing it as the later possible instant for that local datetime - hence the Just another episode in the often weird and wonderful world of time zones. rebuilt with version 20132 01 1.98. The original question would no ionger demonstrate quite the same behaviour. In 2013a, the result would be 358 seconds, with a transition time of 23-54-03 instead of 23:54:08 I only noticed this because I'm collecting questions like this in Noda Time, in the form of unit tests... The test has now been changed, but it just goes to show - not even historical data is safe In TZDB 2014f, the time of the change has moved to 1900-12-31, and it's now a mere 343 second change (so the time between t and t1 IS 344 seconds, it vou see what I mean). To answer a question around a transition at 1900... it looks like the Java time zone implementation treats all time zones as simply being in their standard time for any instant before the start of 1900 UTC: public class Test public static void main(String args) throws Exception Long for (String id : TimeZone getAvailableIDs) Time?one Zone TimeZone.getTimeZone (id); zone. getraworset zone.gecurtsetstart Sustem.out.println(id); The code above produces no output on my Windows machine. So any time zone which has any offset other than its standard one at the start of 1900 will count that as a transition. 1ZDB itself has some data going back earlier than that, and doesn't rely on any idea of a "fixed standard time (which is what getawOffset assumes to be a valid concept) so other libraries need t introduce this artiticial transition edited Mar 27. 2023 at 19:45 9 54 72 newered lul 27. 2011 at 8:31 Jon Skeet 1.4m 873 49186 4 Our is it still accurate? Son Sees

Content Me just removing multithreading from my program instead of fixing the problem: You know, debugging for hours taught me a valuable lesson. The best solution to a problem is usually the easiest one.

Remember when we used to explain our bugs to rubber ducks? Now we just bark orders at AI models to fix our spaghetti code. The evolution from "here's what I've tried" to "just fix it" perfectly captures our descent into tech laziness. Soon we'll just grunt and expect the AI to read our minds. Progress, I guess? At least the duck never judged our variable naming conventions.

Content mCC Follow mcclure111 In C we don't say "Missing asterisk" we say "error C2664: 'void std:vectorblock,std:allocatorTy:push back(const block x)': cannot convert argument 1 from 'std.: Vector iteratorstd.: Vector valstd.: Si mpletypesblock' to 'block '" and i think that's beautiful 4:30 PM - 1 Jun 2018 292 Retweets 926 Likes 20 17 292 926

Content IF THE WORLD WAS CREATED BY A PROGRAMMER IN THe BEGINNING, THERE WAS ThE hEaven AND THE EARTH BUT THE EARTH WAS FORMLESS AND BUGGY, WITHOUT DOCUMENTATION BY toggl AND THE PROGRAMMER SAW THAT IT WAS NOT GOOD THEN YOU SAID "LET THERE BE LIGHT! BUT ThE LIGHT Did NOT COMPILE. On THE SECOND DAY YOU MERGE WATER YOU CREATE HACK SO THAT LIGHT IS PART OF THE LAND TO CREATE DARKNESS, YOU NEED TO HIDE THE LAND, BUt That's OK CAUSE CREATURES WONT BE ADDED UNTIL LATER. AND STACKOVERFLOW SAID IT'S FINE Wherev BUT BECAUSE OF ThE DEPENDEncY, LIGHT BREAKS AS LAND IS ACCIDENTALLY CLOODED YOU CHECK STACKOVERFLOW (IN THE DARKNESS) IT'S ThE THIRD DAY. YOU TRY TO ADD CREATURES YOU ADD THEM IN THE TURNS OUT the CREATURES IN THE DARKNESS, BUT BROWSER USINg COoKIES, NEEDED TO BE ADDED SOONER, THERE'S NO LAND WITHOUT we Tart UNFORTUNATELY MAKES THEM MORTAL BuT The CLienT FOrGoT to LIGHT, AND YOU CAN'T HAVE LIGHT BECAUSE OF THE MENTION THAT WATER IT's THE FOuRTH DAY. YOU DECIDE TO USE C YOU ALSO USE ST TURNS OUT THE ISSUES TO CREATE A BALLOON FOR ABSTrACTIONS,AND THAT INFLATES THE EARTH IT WORKS OUT GREAT WERE CAUSED BY THE WITH FLAT EARTH DESIGN COMPLICATIONS WHATSOEVER! IT'S THE FIFtH DaY YOU START ADDING PeOPLE TO HELP YOU ON THE SIXTH DAY YoU LOOK AT THe CHAOS YOU CREATED ON THE SEVENTH DAY YOU REALLY WANT TO REST BUT YoU NEED To ORGANISE ALL YoU'VE CREATED DANGLING POINTE YOU DECIDE TO CREATE THEM IN YOUR LIKENESS, WHICH IS A MISTAKE REACT THEY IMMEDIATELY POPULATE THE EARTH WITH HACKS FADS AND UNNECESSARY JAVASCRIPT LIBRARIES FUCKIT.JS) SQUERI YOU ATTEMPT TO LEAD PEOPLE BACK TO SENSIBLE PROGRAMMING, BUT IT IS TOO LATE- EVERYTHING RUNS ON DEPENDENCIES. DAVTIMEAIR.JS HORMONE SEA.JS REALISTIC.WAVES.JS BETTERBANKS.JS BASE.JS GIRAFFE.JS SUNDE MONGODB TOGGL.COM MART VIRKUS '17

Complaining about network issues one second, playing Chrome's offline dinosaur game with religious dedication the next. Nothing transforms a senior developer into a prehistoric gaming enthusiast faster than the WiFi dropping. That little T-Rex becomes your best friend during sprint planning calls when your router decides it's time for an unscheduled vacation. The true irony? After 7 years building network infrastructure, I still find myself jumping cacti instead of, you know, actually fixing the connection.