Developers Only Want One Disgusting Thing

Content FBI FBI Google Killing a child Google Killing a child process stackoverflow

OMG, the ABSOLUTE TRAGEDY of modern development! 😭 Left side: that magical moment when ChatGPT hands you the PERFECT solution on a silver platter (or orange, in this case). Right side: the rest of us programmers, DESPERATELY grabbing at that same solution like we've discovered the last chocolate bar on earth! The sheer DRAMA of it all! We're all just monkeys fighting over the same StackOverflow answers that ChatGPT regurgitates with confidence, while we're over here having existential crises about whether we even remember how to write a for-loop without AI assistance! The circle of developer life is now complete - from stealing code to having code stolen from us by our AI overlords!

Content 1.3 KS 8 41 (06 02:28 Fr System information JULIVE VICOO unknown W Source method unknown YC Wit te Line number O Stack trace java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack available Network name Singtel Phone type GSM Network type LTE Network MEr rads

Content Me: gathers the courage to ask my first question on stackoverflow First answer DEVPUNS Duplicate, You fucking donkey.

Content Tweet Angelica Reyes missanjreyes Never mock a beginner, especially when they're working hard to get better. When they ask "stupid questions", just respond and patiently guide them. No need to mock because chances are, they really don't know what to do and they trust that you can help them. 3:43 PM 16 Aug 20 Twitter for Android ill View Tweet activity 3,827 Retweets and comments 12.4K Likes ProgrammerHumor.to

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