- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Out of curiosity I Googled "swag slow-carb quinoa vhs typewriter". Apparently it's quite a popular dish.
Admin
Seitan squid craft beer? This hipster gentrification has gone too far! Time to Occupy Shoreditch!
Admin
I for one would prefer +1 typewriter kitsch.
Admin
Google Translation of the German:
Admin
Read the first screenshot carefully. There is no WTF there. 2/29/2023. There was no leap day in 2023 - it's 2024 this year. Seems more like a PEBKAC or ID10T error than a WTF/Code Failure
Admin
TRWTF is of course the m/d/y date format.
Admin
Rob: This is an error that the software throws upon logging in, even with their built-in administrator account. I submitted a request with the software vendor and the tech who called me back told me that he was dealing with calls from all "900 customers" on the 29th. The solution was to have them advance the system date forward and apply an SQL fix, so no, this is not an ID10T error.
I assume they were building an date in SQL by doing 'current month + current day + current year - 1' and the SQL parser identifies that as a bad date.
Admin
The internet has been a real boon for people doing genealogy. But, as today's article points out, infant deaths in the record show just how bad life was in the past. My Brother's Keeper database of my own family has a large percentage of children age 0... and those are just the ones I know about. I like to grouse about technology (and those who misuse it) as much as the next guy, but I'm glad I'm alive in 2024 and not in 1824.
Admin
It's pretty likely that some code tries to find "the date one year ago", and didn't use their date library correctly. I'd say that's a WTF.
Admin
I could find a use for that Lorum Ipsum nonsense. Suppose I offer up a pageful of that whenever one of those pesky search bots comes to call? The indexing could get somewhat interesting!
Admin
Bitte lege Diskette 2.
Admin
I wonder if ChatGPT and friends can recognize this stuff and omit it, or if someday I'll ask about swag and be told it's slow-carb and usually made with quinoa.
Admin
I've been struggling to come up with a bogus date calculation that fails to account for leap years and makes the software fail precisely on 29th February.
Admin
Maybe not yesterday's WTF, but certainly one. How do you write code that produces a Feb. 29 date string in a non-leap year? Assuming all months have the same length is not something you can easily get away with. Is it non validated input? Did it try to calculate a 1 year interval from yesterday? So many questions...
Admin
I was assuming it was one year before the entered date - "everyone" knows that if you want to know the date one year ago, you simply substract one from the year.
Of course, it remains to be seen what happens if an enterprising Pratchett fan (or their mother?) enters the date as the 16th of Grune in the year of the Pensive Tables.
Admin
Or it was a typed-in date, and a user that still forgets it's not 2023 any more. I've done that.
Admin
Oh yeah, try randomizing the words in Lorem Ipsum and push them into Google Translate. You get some gold nuggets: https://talkwards.com/2011/09/03/pure-silence-is-added-whenever-possible/
Admin
@Álvaro González: I think it's real simple.
Somebody has a homemade date-as-string to date-as-object parsing routine. Which routine rejects Feb 29 in years there isn't one. Like the 2023 in the example.
Admin
I’m vegan, so I just have to try some of that qui mustache tofu.
Admin
Leap day in New Zealand has an impressive leap day bug when all pre-pay petrol (gasoline) pumps died because of a leap day bug. It took until the afternoon on Feb 29 to fix it.
Admin
You could spot the reactions to the problem that came from IT people, "I bet that code was less than three years old". It's kinda depressingly predictable that you can hear about an IT problem and almost immediately know which Standard Mistake it was caused by.
Admin
I can't wait until January 19, 2038..
Admin
So lemme get this right ... you want to run Debian AMD64/Intel64 code on the ARM based Pi? Sounds fair...
Admin
Sounds like you found findagrave.com then. That's a truly amazing resource from genealogists, largely built upon volunteers getting cemetery records.
Now I think I should go home and check how many people in my database were born (or died) on February 29.
Admin
The hipster stuff is probably from Hipster Ipsum: https://hipsum.co/.
My favorite Lorem Ipsum knockoff is "Samuel L Ipsum" featuring Samuel L Jackson quotes; extremely NSFW: https://slipsum.com/.
Admin
Nah, instead of taking a date and subtracting a year, they're taking the year and subtracting one to get an invalid date...
Admin
"Flexitarian Pitchfork forage" sounds like a competitive food-gathering event...
Admin
My February 29th bug was code that built a date by components (year=x, month=y, day=z). Each component is optional. If you set year=2023 and the other two fields blank, it would default to today's month and day, get Feb 29th 2023, and crash.