• Hanzito (unregistered)

    A frist thing happened.

  • (nodebb)

    A thrid thing happened

  • DQ (unregistered)

    And then a scnd thing

  • (nodebb)

    This is one of those so obvious so dumb things that it's hardly WTF worthy.

    I don't know those particular syscalls, but was there any good reason they couldn't have simply replaced the call to the first with the call to the second then output all the date & time components from that result value?

    Looks to me like another example of doing without thinking. And of "the best change is the smallest change". Both of which are shortsighted crap pushed by ignorant managements. Faster isn't better when you have to do it twice to get it right. Or more.

  • Hanzito (unregistered) in reply to WTFGuy

    This is one of those so obvious so dumb things that it's hardly WTF worthy.

    You may think so, but the other day, I saw an announcement for some kind of "no code" declarative thingy that translates to SQL and JavaScript (and something else), which was vibe-coded and had this exact same error in the example on the front page. Nobody seemed to notice it. So there's that...

  • (nodebb) in reply to WTFGuy

    I don't know those particular syscalls, but was there any good reason they couldn't have simply replaced the call to the first with the call to the second then output all the date & time components from that result value?

    No, there wasn't a good reason. That's why it's a WTF and posted on this site.

Leave a comment on “Well Timed Double Checking”

Log In or post as a guest

Replying to comment #690226:

Log Out

« Return to Article