And I Write Garbage Professionally

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 So many furries in one flight. Tag them if you know them! 7:27 PM 102521 Twitter for Android 1,017 Retweets 1,448 Quote Tweets 8,144 Likes 14h I object to that many Furries being on the same airplane because if there were an accident it could basically cripple the American IT industry in an instant.

Content e4moji e4moji If I had a nickel for every time I got confused, I'd be like "where'd this nickel come from?" and then there'd be another nickel and I'd think "what's with the nickels?" leading to more nickels and confusion and eventually I'd be slowly crushed by nickels without ever knowing why

You think you're hunting down a simple bug, but then you find the actual monster behind it. That tiny green bug wasn't the issue—it was just the symptom of the hulking Spring framework beast lurking in your codebase. Nothing says "I'm having a normal one" like realizing your quick fix just turned into a complete architecture overhaul. Happens every Tuesday.

OH. MY. GOD. The absolute GENIUS of this meme! 🤣 Each programming control structure represented by its perfect power cord equivalent: • if-else chains : Multiple dongles hanging off your laptop like some desperate octopus trying to connect to EVERYTHING • switch : A literal power SWITCH with multiple outlets (I mean, come ON with that perfection!) • while(True) : A power strip connected TO ITSELF in an infinite loop that would make your electrical inspector have a stroke • foreach : Power strips daisy-chained along the wall like some kind of electricity conga line • try : That chaotic rat's nest of cables we ALL have somewhere but pretend we don't • catch : A circuit breaker ready to save your entire house from burning down when your code inevitably fails And we all know that "Build Skip Tests" means we're bypassing ALL these safety measures anyway! Who needs error handling when you have deadlines?!

The eternal struggle between modern and traditional null-checking approaches! The top shows Kotlin's fancy safe call operator ( nullableThing? ) with the let block—a one-liner that handles nulls elegantly. Meanwhile, the bottom shows the old-school explicit null check with an if statement that your grandfather probably wrote in Java back when dial-up internet was still cool. Developers with Stockholm syndrome for verbose code are nodding in agreement with "Embrace tradition" while secretly knowing the top version is objectively better but requires learning something new. It's like choosing between a smart electric car and a gas-guzzling muscle car because "they don't make 'em like they used to!"