# The Daily WTF

Curious Perversions in Information Technology

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## CodeSOD: A Living Fossil

DevFeed: [CodeSOD: A Living Fossil](<https://devfeed.tech/articles/codesod-a-living-fossil-144729.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/a-living-fossil>)

Author: Remy Porter

Published: 2026-11-19T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [CSS](<https://devfeed.tech/topics/css.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [codesod](<https://devfeed.tech/tags/codesod.md>)

### AI overview

An intranet page still receiving updates uses table-based layout, repeated line breaks, empty cells, and a sidebar border image--patterns the author describes as a surviving example of older web design. The markup suggests it may have begun in a WYSIWYG editor such as Dreamweaver, while HTML comments and later text-editor edits indicate that people also worked directly in the code. The lack of CSS points tentatively to an older site; self-closing `
` tags provide a more specific period clue. The author says the site is being replaced and jokes that it deserves a historical marker.

### Source excerpt

Today's anonymous submission is a blast from the past. This comes from an intranet HTML page that has been receiving continuous updates for some time. How long? Well, let's take a peek at how it does its layout. <b>Extension:</b> x5555
 <b>Email:</b>: <a href="mailto:blahblah@example.com"></a>

 </td> <td width=140> </td> </tr> <tr><td>&nbsp;</td></tr> <tr><td>&nbsp;</td></tr> </td> </table> </center> <!-- END DIRECTORY --> <tr><td>
</td></tr> </td> </tr> </table> <!-- MATERIAL ENDS HERE --> 
 
 </td> </tr> </table> </center> </td> </tr> <tr><td width=987 height=4 background="../images/table_bottom_sidebar.jpg"></td></tr> </table> This is like a coelecanth, or a horeshoe crab. A living fossil. There are hints that imply this started life as the output of a WYSIWYG editor, like Dreamweaver or something. The loads of line break tags, the table cells that contain only a space, and also the one table cell that contains a line break- that feels like a WYSIWYG trying to interpret what the user types. But the comments imply someone was also looking at the HTML code at some point. And certainly, in the modern era, it is being edited by someone with a text editor. The absence of CSS might point us towards a late 90s website, as by the early 00s, CSS was starting to become standard, but the thing that really pins this in a point in time is the XHTML style self-closing 
 tags. But then little quirks highlight that someone was also getting "creative" with code. The table_bottom_sidebar.jpg had related images, all designed to put borders in the table. There were matching images for left, right, and top borders. Our submitter adds: "Needless to say, this site is being replaced." Replaced? It should get a historical marker. This is how we used to do it, in the bad old days. We'd add 
&nbsp; while churning butter in homespun dresses, and we liked it. Okay, we didn't like it. But still. [Advertisement] Keep all your packages and Docker contain

## Representative Line: Terning White as a (Style)Sheet

DevFeed: [Representative Line: Terning White as a (Style)Sheet](<https://devfeed.tech/articles/representative-line-terning-white-as-a-style-sheet-141923.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/terning-white-as-a-style-sheet>)

Author: Remy Porter

Published: 2026-11-18T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [PHP](<https://devfeed.tech/topics/php.md>), [if statement](<https://devfeed.tech/topics/if-statement.md>)

Tags: [boolean](<https://devfeed.tech/tags/boolean.md>), [conditional](<https://devfeed.tech/tags/conditional.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [easy](<https://devfeed.tech/tags/easy.md>), [examples](<https://devfeed.tech/tags/examples.md>), [formatting](<https://devfeed.tech/tags/formatting.md>), [helpdesk](<https://devfeed.tech/tags/helpdesk.md>), [idea](<https://devfeed.tech/tags/idea.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [php](<https://devfeed.tech/tags/php.md>), [processing](<https://devfeed.tech/tags/processing.md>), [regular](<https://devfeed.tech/tags/regular.md>), [representative-line](<https://devfeed.tech/tags/representative-line.md>), [shouldn-t](<https://devfeed.tech/tags/shouldn-t.md>), [style](<https://devfeed.tech/tags/style.md>), [support](<https://devfeed.tech/tags/support.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [team](<https://devfeed.tech/tags/team.md>), [templating](<https://devfeed.tech/tags/templating.md>)

### AI overview

The excerpt's finding is that `$bgc = $tno ? '#FFFFFF' : '#FFFFFF';` contains an unnecessary ternary: both outcomes assign the same color, and `$tno` is a numeric value that may be zero but should not determine formatting. The excerpt says the condition was typed directly, rather than generated by a template or preprocessing step.

### Source excerpt

Years ago, Stefan's company was short handed, especially on the developer team. But they had a large hell-desk support team. And at some point, someone had the genius idea: "PHP is easy for anyone to learn, and so our helpdesk folks should have no problem. Let's hand them development tasks." Which meant Stefan inherited lots of lines which look like this: $bgc = $tno ? '#FFFFFF' : '#FFFFFF'; Unlike many examples of this pattern, this is not the result of a pre-processing or templating step generating a conditional where both branches are the same value. Someone actually typed this. Also, notably, the variable $tno holds a numeric value, not a boolean, and is never null. It sometimes is zero, which is false, but zero is just a regular value it might hold, and thus it shouldn't get any special formatting. In short, the ternary shouldn't be here, not just because both branches are the same thing, but because there shouldn't logically be any branching at all. [Advertisement] ProGet's got you covered with security and access controls on your NuGet feeds. Learn more.

## CodeSOD: Building a Line

DevFeed: [CodeSOD: Building a Line](<https://devfeed.tech/articles/codesod-building-a-line-139424.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/building-a-line>)

Author: Remy Porter

Published: 2026-11-17T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [concatenation](<https://devfeed.tech/topics/concatenation.md>), [IO](<https://devfeed.tech/topics/io.md>)

Tags: [abstraction](<https://devfeed.tech/tags/abstraction.md>), [builder](<https://devfeed.tech/tags/builder.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [concatenation](<https://devfeed.tech/tags/concatenation.md>), [file](<https://devfeed.tech/tags/file.md>), [function](<https://devfeed.tech/tags/function.md>), [performance](<https://devfeed.tech/tags/performance.md>), [return](<https://devfeed.tech/tags/return.md>), [string](<https://devfeed.tech/tags/string.md>)

### AI overview

The function reads a file in full, adds a line feed to the resulting string, appends that single combined value to a StringBuilder, and returns it. The author calls this a superstitious use of StringBuilder: for the current task, returning the read contents plus a line feed is simpler. Separate StringBuilder appends could make sense if the output were expected to grow or change, but the author considers that setup premature abstraction here.

### Source excerpt

There's an unofficial category of posts here that I call "Somebody told us string builders were more efficient, so we always use string builders, regardless of whether or not that actually makes sense," or STUSBWMESWAUSBROWONTAMS, for short. Probably should workshop that name some. In any case, Adam sends us a new entry for that collection: Public Function ReadFromFile(ByVal filename As String) As String Dim sb As StringBuilder = New StringBuilder() Dim str As String = String.Empty Using sr As StreamReader = File.OpenText(filename) str = sr.ReadToEnd() sb.Append(str & Constants.vbLf) End Using Return sb.ToString() End Function This function takes a filename, opens a file, reads the entire contents of the file to a variable. It concatenates a line feed to the end of the string it just read, then appends all of that to a string builder. Finally, we return sb.ToString(), taking the single string in the string builder, appending nothing to it, and returning the result. I'd almost, almost forgive the code if it was more like: str = sr.ReadToEnd() sb.Append(str) sb.Append(Constants.vbLf) You're not actually gaining much from this, but it follows the broad pattern of "use a string builder" so that if you ever wanted to change the structure of the output, you're already set up to prepend/append new text in a scalable way. I'd argue that's premature abstraction, though: a simple return sr.ReadToEnd() & Constants.vbLf would do the current job. The code that we have is a clear superstitious use of string builders. The string builder is used as a charm against poor performance, without understanding why one might use it, or how it might work; string concatenation means string builder, always and forever, "why" doesn't enter into it. [Advertisement] Keep all your packages and Docker containers in one place, scan for vulnerabilities, and control who can access different feeds. ProGet installs in minutes and has a powerful free version with a lot of great features that you can upg

## Unenumerbrated

DevFeed: [Unenumerbrated](<https://devfeed.tech/articles/unenumerbrated-136390.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/unenumerbrated>)

Author: Ellis Morning

Published: 2026-11-16T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [enum](<https://devfeed.tech/topics/enum.md>), [data type](<https://devfeed.tech/topics/data-type.md>)

Tags: [client](<https://devfeed.tech/tags/client.md>), [count](<https://devfeed.tech/tags/count.md>), [database](<https://devfeed.tech/tags/database.md>), [enum](<https://devfeed.tech/tags/enum.md>), [feature-articles](<https://devfeed.tech/tags/feature-articles.md>), [has](<https://devfeed.tech/tags/has.md>), [index](<https://devfeed.tech/tags/index.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [payments](<https://devfeed.tech/tags/payments.md>), [queries](<https://devfeed.tech/tags/queries.md>), [string](<https://devfeed.tech/tags/string.md>)

### AI overview

A MySQL column defined as `enum('0', '1')` caused confusing query results because enum values are strings, while unquoted integer comparisons can refer to their 1-based enum indices. Thus `successful='1'` compares with the string value, whereas `successful=1` compares with the first enum index, `'0'`. The author recommends using descriptive enum labels such as `successful` and `unsuccessful` instead of numeric-looking labels. The excerpt also notes that some ORM or query-builder frameworks quote values and rely on MySQL's conversions, adding to the confusion.

### Source excerpt

Submitter Valts shares an enumerated mystery: This happened a few years ago (before COVID). A colleague called me over because he couldn't make sense of the results he was getting from some MySQL queries in MySQL Workbench. I don't remember the queries in particular, but let's say select * from payments where client_id=1234 showed 12 rows, all having the successful field set to 1. But when you selected select count(*) from payments where client_id=1234 and successful=1 you got back 0 rows. And this was reproducible on my machine, too. Yet in code similar queries worked just fine. After a lot of head-scratching and increasingly bizarre hypotheses, we finally figured out what was going on. In the far, far past, in dark days gone by, someone had defined the database field as enum('0', '1'). This SEEMS pretty rational ... until you start reading up how MySQL treats enums. Enums, it turns out, are all STRING values. But in queries you can use either their string values, or their integer indices, starting at 1. So in this case, the string "0" has the integer index of "1", and the string "1" has the integer index of "2". So select * from payments where successful='1' is quite different from select * from payments where successful=1. For extra confusion, under most other circumstances MySQL normally silently converts between strings and integers as needed. Some ORM/QueryBuilder frameworks even simply quote ALL values and let MySQL handle the conversions. Facepalms were had. In the aftermath, I blame the person who defined this field more than I blame MySQL for its bizzare enum conventions. If you're doing enums (which are generally a good thing), then give them proper names like successful and unsuccessful or something. Not 0 and 1. This code and this database table is still in use today, but luckily it's the only such gotcha in the entire system. Enums in the database are scarce and the rest of them are sane. [Advertisement] Keep all your packages and Docker containers in

## Error'd: The Artist Formerly Known As

DevFeed: [Error'd: The Artist Formerly Known As](<https://devfeed.tech/articles/error-d-the-artist-formerly-known-as-133500.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/the-artist-formerly-known-as>)

Author: Lyle Seaman

Published: 2026-11-13T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Error Handling](<https://devfeed.tech/topics/error-handling.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [car](<https://devfeed.tech/tags/car.md>), [code](<https://devfeed.tech/tags/code.md>), [decoding](<https://devfeed.tech/tags/decoding.md>), [dialog](<https://devfeed.tech/tags/dialog.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [email](<https://devfeed.tech/tags/email.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [error](<https://devfeed.tech/tags/error.md>), [error-d](<https://devfeed.tech/tags/error-d.md>), [leak](<https://devfeed.tech/tags/leak.md>), [pizza](<https://devfeed.tech/tags/pizza.md>), [ship](<https://devfeed.tech/tags/ship.md>), [solution](<https://devfeed.tech/tags/solution.md>), [source](<https://devfeed.tech/tags/source.md>), [source-code](<https://devfeed.tech/tags/source-code.md>), [strings](<https://devfeed.tech/tags/strings.md>), [tools](<https://devfeed.tech/tags/tools.md>), [toyota](<https://devfeed.tech/tags/toyota.md>), [trade-in](<https://devfeed.tech/tags/trade-in.md>)

### AI overview

The excerpt collects examples of confusing or erroneous messages: a Toyota trade-in email missing key words, a shipping delay dated before the sender and recipient were born, a request to backdate a refund, and a pizza coupon that could not be applied as expected. It also mentions nullable drivers and a powerbank rental station error dialog, then raises questions about whether the dialog exposes source code and what tools built the website. No specific fixes or answers are provided.

### Source excerpt

"You want my what?" The artist formerly known as Toyota has a proposition for Chris. "Toyota wants me to trade in my current car, but the email was missing a few words." Just another ordinary zero date here, from Hercules "I wanted to ship a gift for my sister. I understand delays, but it's going to be delayed to before either of us were born?" He also reported that another page demonstrated the possibility of nullable drivers which is either terrifying or just proof of more automation. Or both. "Can you back date my refund?" Totty reasonably requests. "Thanks for the timely update" WeaponizedFun has some Coupon Confusion. Too hungry; didn't read. "I would have thought ordering a two-topping pizza combo would have been easier, but apparently there are only specific ways I can use this coupon that still leave me scratching my head. Ultimately, the coupon wasn't applicable to what I wanted to order, so I guess I'll never know." appas wonders regarding this error dialog from a powerbank renting station "Does this qualify as a source code leak?" Personally, I wonder if someone can identify the tools used to build this website. I frequently find myself struggling with encoding/decoding/armoring strings and I also wonder if anyone anywhere has a good solution. [Advertisement] ProGet's got you covered with security and access controls on your NuGet feeds. Learn more.

## CodeSOD: Next Month

DevFeed: [CodeSOD: Next Month](<https://devfeed.tech/articles/codesod-next-month-131106.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/next-month>)

Author: Remy Porter

Published: 2026-11-12T06:30:00Z

Content type: news

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [if statement](<https://devfeed.tech/topics/if-statement.md>)

Tags: [billing](<https://devfeed.tech/tags/billing.md>), [bug](<https://devfeed.tech/tags/bug.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [net-9](<https://devfeed.tech/tags/net-9.md>)

### AI overview

A billing bug canceled all bills due in January because the code compared only the month numbers of `next_bill_date` and `end_date`, ignoring the year. When December began, January's month number was greater than or equal to the account's ending month, so the code cleared and saved those billing dates. The team could reconstruct the dates without restoring a backup, but an unknown number of customer billing periods had been canceled and required a history check.

### Source excerpt

One of Sean's colleagues left Initech on good terms. It caused no small amount of surprise that the very next day their billing system started failing. The billing system which the colleauge had worked on. No one truly suspected foul play, it was just a weird coincidence. Still, billing blowing up was a 5 alarm fire, so everyone was throwing every idea out about what could be the cause. Late in the evening, after staring at the code for many hours, Sean found this: if item.next_bill_date.month >= end_date.month item.next_bill_date = nil item.save else ... end If the month of the next billing date is greater than the last billing date for this account, wipe the billing date and update the item. It's worth noting that Sean's co-worker's last date happened to be the end of November, and billing started blowing up on the 1st of December. You'll also note this is checking just the month and not any other part of the date, like, oh, I don't know, the year? While this bug could happen to any bill, it was blowing up in December because every bill's ending month was greater than or equal to January. So this code canceled all the bills due in January. The good news was that they could reconstruct the correct next billing dates without having to restore from a backup. The bad news is that some unknown number of billing periods had been canceled for some of their customers, and someone was going to have to check the history. Sean reached out to his former co-worker to politely thank them for an early Christmas present. "At least I understand our billing code better," Sean writes. [Advertisement] Plan Your .NET 9 Migration with Confidence Your journey to .NET 9 is more than just one decision.Avoid migration migraines with the advice in this free guide. Download Free Guide Now!

## In the Hole

DevFeed: [In the Hole](<https://devfeed.tech/articles/in-the-hole-129684.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/in-the-hole>)

Author: Remy Porter

Published: 2026-11-11T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [hosting](<https://devfeed.tech/topics/hosting.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alpine](<https://devfeed.tech/tags/alpine.md>), [container](<https://devfeed.tech/tags/container.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [feature-articles](<https://devfeed.tech/tags/feature-articles.md>), [glibc](<https://devfeed.tech/tags/glibc.md>), [libc](<https://devfeed.tech/tags/libc.md>), [linux](<https://devfeed.tech/tags/linux.md>), [musl](<https://devfeed.tech/tags/musl.md>), [security](<https://devfeed.tech/tags/security.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [sshole](<https://devfeed.tech/tags/sshole.md>)

### AI overview

The excerpt describes an SSH authentication flaw on some Linux systems: passwords longer than 256 characters can trigger a failed hash that lets a passwordless account authenticate. The account check compares the returned hash with the stored value. In glibc, `crypt` reports invalid input with `NULL`; in musl, it returns `*`, the same value commonly used in `/etc/shadow` or `/etc/passwd` to disable password access. The text says this affects musl-based systems such as Alpine, including containers, and reports that the flaw is being exploited. It attributes the failure to the interaction between musl's error return, the stored marker, and a password-length cap. The supplied excerpt ends before the article's full discussion.

### Source excerpt

Look, I don't want to keep talking about security issues. Blame AI. Just another thing it ruined. At this point, you've probably heard about *sshole. If you haven't, the quick summary: on some Linux systems, SSH will log you in to an account with no password if you supply a password greater than 256 characters long. Frequently, you might make accounts like root nominally inaccessible by giving it no password, so this is a big deal. Worse, it impacts varieties of Linux that use the musl implementation of libc, like Alpine- the kinds of varieties that run inside a container hosting a web app somewhere. The impact is broad, and is definitely being exploited. The root cause, however, is interesting, because it's a sum of very simple choices that lead to a wildly undesirable result. The core function in question is crypt, a stardard part of the C library. crypt is already not the best name, as it's a hashing function, but its behavior is pretty clear. Pass it a string and a salt, and it gives you a hashed version of the password suitable for storing in your /etc/shadow file. Now, the man page has the answer to the important question: what happens when I hand the function invalid inputs, like a bad salt? In the glibc implementation, it returns a NULL. That's a pretty standard C-style method of handling errors: I failed to do the thing, so I'm going to return a NULL value. This puts the onus on the callers to correctly handle the NULL (which also handles the error). glibc isn't the only implementation of libc, though. There are many others, each tuned to different types of runtime environments. For example, uClibC is a minimal implementation specifically designed to make lightweight executables that can run in resource constained environments. It makes tradeoffs that make it less desirable for a desktop or server environment. musl attempts to do both: be lightweight and suitable for embedded environments and also suitable for server environments. This makes musl a great ch

## CodeSOD: Plenty of IDs

DevFeed: [CodeSOD: Plenty of IDs](<https://devfeed.tech/articles/codesod-plenty-of-ids-127496.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/plenty-of-ids>)

Author: Remy Porter

Published: 2026-11-10T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [Code Modularity](<https://devfeed.tech/topics/code-modularity.md>), [identifier](<https://devfeed.tech/topics/identifier.md>)

Tags: [codesod](<https://devfeed.tech/tags/codesod.md>), [ids](<https://devfeed.tech/tags/ids.md>), [net](<https://devfeed.tech/tags/net.md>), [net-9](<https://devfeed.tech/tags/net-9.md>)

### AI overview

A Python VM launcher generates five-digit identifiers by sampling five distinct digits from 0-9, which limits the pool to 30,240 values rather than all 100,000 five-digit strings. The excerpt says this small pool brings a 1% collision chance after 26 requests and a 50% chance after 206, illustrating how quickly duplicate identifiers can occur despite the seemingly large number of possibilities.

### Source excerpt

Venkat joined a new team in the middle of a big refactoring effort. The code was quite a mess, glued together by long Python scripts with main functions longer than a Tolstoy novel. It was this effort to clean up the code into neat modules that highlighted some logical issues with their implementation. def generate_random_number(): """ Generate a 5 digit random number. """ return "".join(map(str, random.sample(range(0,10),5))) The script this function comes from is a launcher script that provisions a VM to execute code. The VM needs a unique identifier, and we get that random number this way. The random.sample function, in Python, samples a population without replacement. So here, we pass it a range of 0-10 (which is 0-9 inclusive), and ask for five random entries from it. Again, without replacement, so a range that could concievably contain up to 100,000 possible values is significantly constrained down to 30,000 or so- only the numbers less than 100,000 that contain no duplicate digits. We then map the resulting array into an array of strings, then join that into a final output string. Now, for most of us, I do suspect that 30,240 unique values is probably enough for how ever many VMs we might need to reserve at any one time; if you're not working for Amazon or Google or whatever, you're probably fine. Then again, the chances of an accidental collision are surprisingly high: after only 26 requests, there's a 1% chance of a collision. And thanks to the birthday problem, it takes 206 requests to get to a 50% chance of collision. So maybe 30,240 is not enough for anybody. [Advertisement] Plan Your .NET 9 Migration with Confidence Your journey to .NET 9 is more than just one decision.Avoid migration migraines with the advice in this free guide. Download Free Guide Now!

## CodeSOD: Eventually

DevFeed: [CodeSOD: Eventually](<https://devfeed.tech/articles/codesod-eventually-124205.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/eventually>)

Author: Remy Porter

Published: 2026-11-09T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [code comments](<https://devfeed.tech/topics/code-comments.md>), [To-Do](<https://devfeed.tech/topics/todo.md>)

Tags: [codesod](<https://devfeed.tech/tags/codesod.md>), [comment](<https://devfeed.tech/tags/comment.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>)

### AI overview

A TODO comment says a method ideally belongs in the tax framework, but was duplicated under time pressure and should later be refactored. The excerpt says the comment has remained unchanged for 23 years and the refactoring never happened.

### Source excerpt

We were just discussing TODO comments recently, and that motivated Bernard to send us this representative comment.. // TODO: This method should ideally be in tax frame work but due to // the time constraint I am duplicating the code here. // Needs to be refactored. Oct 28, 03. This comment exists in this codebase, unchanged. It has been there for twenty three years. The refactoring has never happened. This comment has seen the world change over the last 23 years, as the technology landscape has shifted and changed, grown and contracted. But this comment, this comment is a constant. [Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!

## CodeSOD: Only Create Me if I Exist

DevFeed: [CodeSOD: Only Create Me if I Exist](<https://devfeed.tech/articles/codesod-only-create-me-if-i-exist-119673.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/only-create-me-if-i-exist>)

Author: Remy Porter

Published: 2026-11-05T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [sql-server](<https://devfeed.tech/topics/sql-server.md>), [sql-database](<https://devfeed.tech/topics/sql-database.md>), [SQL](<https://devfeed.tech/topics/sql.md>)

Tags: [codesod](<https://devfeed.tech/tags/codesod.md>), [constraint](<https://devfeed.tech/tags/constraint.md>), [database](<https://devfeed.tech/tags/database.md>), [foreign-keys](<https://devfeed.tech/tags/foreign-keys.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [table](<https://devfeed.tech/tags/table.md>)

### AI overview

The excerpt shows a SQL Server constraint that makes `ListingDetails.Id` a foreign key to the same table's `Id`. Unlike a typical self-reference between different rows, each record satisfies this constraint with its own ID, so the author says it appears to work as a no-op. The author notes they have not tested it personally and bases that conclusion on cursory searching.

### Source excerpt

Foreign keys are an important part of making sure the entities in our relational database can be connected back together and queried correctly. It's part of proper data normalization. This isn't shocking, of course: the order line table has a foreign key over to the products table, so that every line item points to a product we sell. That's database 101. Database 201, you'd also think about the times where you have a hierarchy of records, where say, every Employee has a ManagerId, which is a foreign key back to the Employee table itself (and in database 301, you'll understand why having a ManagerId field is a terrible choice, but that's neither here nor there). The important thing here is that foreign keys are very common, and foreign keys pointing back to the same table are also very common. But it can still go very wrong. Roman sends us this foreign key definition in a database they maintain. ALTER TABLE [dbo].[ListingDetails] WITH CHECK ADD CONSTRAINT [FK_Listings_Listings] FOREIGN KEY([Id]) REFERENCES [dbo].[ListingDetails] ([Id]) This ensures that the ListingDetails table's Id field is a foreign key over to the ListingDetails table's Id field. A field is a foreign key back to itself. Roman writes: "I can't believe SQL Server even allows this..." I can. While I haven't personally tried this out, a bit of cursory searching implies that this does actually work- the record satisfies its own constraint, so you can still add it to the database. It's basically a no-op, which isn't great, but it's not SQL Server's job to ensure you keep all your toes because they've removed all the footguns. [Advertisement] Utilize BuildMaster to release your software with confidence, at the pace your business demands. Download today!

## Representative Line: What it Doesn't Do

DevFeed: [Representative Line: What it Doesn't Do](<https://devfeed.tech/articles/representative-line-what-it-doesn-t-do-117823.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/what-it-doesn-t-do>)

Author: Remy Porter

Published: 2026-11-04T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Programming language](<https://devfeed.tech/topics/programming-language.md>), [return](<https://devfeed.tech/topics/return.md>)

Tags: [all](<https://devfeed.tech/tags/all.md>), [code](<https://devfeed.tech/tags/code.md>), [comment](<https://devfeed.tech/tags/comment.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [function](<https://devfeed.tech/tags/function.md>), [representative-line](<https://devfeed.tech/tags/representative-line.md>)

### AI overview

A code comment says `getAllMailers()` neither returns Mailers nor all of them. Blame showed Alastair had written the comment, though he had not written the code. He suggests updating the function name everywhere may have been more work than adding the comment, and leaves open what the function actually returns.

### Source excerpt

Alastair found this comment in his codebase, and wondered, "who wrote this comment?" A quick blame answered the question: he did. He did not, however, write the code. public function getAllMailers() { // This function neither returns Mailers, nor all of them. ... } I suppose the comment was easier to add that doing a global find/replace to update the function name everywhere. But I do wonder, what does this function return? In any case, sing along: "I wrote the comment, but I did not pick this function name". [Advertisement] Keep the plebs out of prod. Restrict NuGet feed privileges with ProGet. Learn more.

## CodeSOD: Death of the Auth-Er

DevFeed: [CodeSOD: Death of the Auth-Er](<https://devfeed.tech/articles/codesod-death-of-the-auth-er-115664.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/death-of-the-auth-er>)

Author: Remy Porter

Published: 2026-11-03T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [conditionals](<https://devfeed.tech/topics/conditionals.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [return](<https://devfeed.tech/topics/return.md>)

Tags: [auth](<https://devfeed.tech/tags/auth.md>), [code](<https://devfeed.tech/tags/code.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [conditionals](<https://devfeed.tech/tags/conditionals.md>), [death](<https://devfeed.tech/tags/death.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [perl](<https://devfeed.tech/tags/perl.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The inherited `store()` handler is effectively disabled by unconditional `die` statements: it stops at `echo 'Hello'`, before attempting authentication. Further `die`s would also halt the success and failure paths, preventing the welcome response or redirect. The author speculates these statements were added while disabling the route path by path, but says the source history is unavailable; the code reportedly remained in production for years.

### Source excerpt

When writing Perl, it's not unusual to want to die. The die function ends your Perl program with an error string, and you'll often see code like: die "My error" unless $i > 5 or die "Other error" if check(), because Perl just loves the backwards conditionals. What's even more fun with die is how it behaves with eval blocks, so it doesn't always kill your program, sometimes it is how you pass error strings back out of sections of your program. And poor Bobby has inherited some Perl that just really loves to die. public function store() { echo 'Hello'; die; if (Auth::attempt(Input::only('email', 'password'))) { echo 'done'; die; // return "welcome ".Auth::user()->username } echo "Oops! Fails"; die; return Redirect::back()->with_input(); } Bobby didn't send the source control history here, but I have a sense of what it likely was like, once. If they authenticate successfully, print a welcome message. If they don't, redirect back to the logon page and let them try again. I suspect they wanted to disable the route. So first they disabled the success path, only to discover that the failure path kept redirecting, so they disabled that too. Finally, they added the Hello at the top to disable the whole thing. Why? Why did they do any of this? No idea. It feels like debugging code, but you'd expect more echos and fewer dies if that were the case. And you wouldn't expect it to leak into production and sit there for years, which is what happened here. [Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!

## CodeSOD: Get It Now

DevFeed: [CodeSOD: Get It Now](<https://devfeed.tech/articles/codesod-get-it-now-112789.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/get-it-now>)

Author: Remy Porter

Published: 2026-11-02T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [code comments](<https://devfeed.tech/topics/code-comments.md>)

Tags: [codesod](<https://devfeed.tech/tags/codesod.md>), [memes](<https://devfeed.tech/tags/memes.md>)

### AI overview

The excerpt shows a TODO left unresolved in Sam C's code: a `getnow` function returns the hard-coded year `'2012'`. The commentary jokes about how unexpectedly long ago 2012 was. The excerpt provides no technical explanation or broader context for the function.

### Source excerpt

"TODO" comments are an inescapable part of our work. Yes, yes, you should just do it right the first time, everything should probably have a ticket in whatever your ticket system is for visibility, but at some point, you're just going to leave a "TODO" behind. But hopefully, the TODO gets TODONE, which is not what happened in Sam C's codebase. function getnow() { //TODO return '2012'; } It's the XKCD, but for years. Or WHAT YEAR IS IN memes. At least it's a relatively recent year, not some far off point from over a decade ago. Wait. 2012 was how long ago? That can't be right. It was just a few years ago! [Advertisement] Plan Your .NET 9 Migration with Confidence Your journey to .NET 9 is more than just one decision.Avoid migration migraines with the advice in this free guide. Download Free Guide Now!

## CodeSOD: Oh, K?

DevFeed: [CodeSOD: Oh, K?](<https://devfeed.tech/articles/codesod-oh-k-107000.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/oh-k>)

Author: Remy Porter

Published: 2026-10-29T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [identifier](<https://devfeed.tech/topics/identifier.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [c](<https://devfeed.tech/tags/c.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [comment](<https://devfeed.tech/tags/comment.md>), [macros](<https://devfeed.tech/tags/macros.md>), [memory](<https://devfeed.tech/tags/memory.md>), [variables](<https://devfeed.tech/tags/variables.md>)

### AI overview

The inner loop uses `k` as its counter, but another statement in the same loop assigns `k = strlen(someOutputString) - 8;`, overwriting that counter. The comment misidentifies this ordinary variable reuse as a memory violation and says `l` is used to work around it. The author suspects the long, complex, macro-heavy loop made the bug hard to find; declaring the loop variable in place would improve scoping but would not fix this clobbering.

### Source excerpt

Pierre found this cry for help: for (j = 0; j < DISTRICT_CARDINALITY; j++) { /* * A poor way to work around some sort of memory * violation. k gets clobbered, so I buffer l with it. * Help? */ for (k = 0, l = 0; k < customers; k++, l++) { /* c_id */ FPRINTF(output, "%d", l + 1); METAPRINTF((output, "%c", delimiter)); Honestly, I'm always a little worried in C-like languages when the loop variable isn't scoped to the loop and declared in place. Always concerning, so when there's concerns with clobbering, I'm not surprised. This iterates across a set of "districts", and then iterates across a list of customers. Standard output functions are replaced with macros, and honestly, I don't know that I want to know what happens in METAPRINTF. But fine, this iterates across a bunch of stuff and generates output. It's the comment that we're really curious about. "Some sort of memory violation", so we duplicate our loop variable. What on earth could be happening here? Well, Pierre found the "memory violation", which is probably what you expected: k = strlen(someOutputString) - 8; k is used elsewhere in the loop as a variable. That's not a memory violation, that's just how variables work. This leaves us with one possible conclusion: the developer who wrote the comment couldn't find this bug. And given the weird use of macros here, I'm going to go out on a limb and guess that it's not the developer's fault; I strongly suspect the loop is so long, so complicated, and so obfuscated that very few developers could find that. My earlier complaint about scoping the variable to the loop wouldn't fix this, which I guess is on me. They still should really scope the variable to the loop. [Advertisement] Keep all your packages and Docker containers in one place, scan for vulnerabilities, and control who can access different feeds. ProGet installs in minutes and has a powerful free version with a lot of great features that you can upgrade when ready.Learn more.

## CodeSOD: Session Recording

DevFeed: [CodeSOD: Session Recording](<https://devfeed.tech/articles/codesod-session-recording-105625.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/session-recording>)

Author: Remy Porter

Published: 2026-10-28T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [sql-database](<https://devfeed.tech/topics/sql-database.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [asp-net](<https://devfeed.tech/tags/asp-net.md>), [autocomplete](<https://devfeed.tech/tags/autocomplete.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [database](<https://devfeed.tech/tags/database.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>)

### AI overview

The Web Forms snippet reads an album ID from a control, stores it in session, builds and executes a SQL DELETE query using that ID and the session user ID, then redirects. The author criticizes the indirect FindControl-to-Label lookup, using a label to hold input, and the concatenated query as vulnerable to SQL injection. They also question storing the query in a page member and criticize broad use of session state, including for form inputs and loop variables. The redirect's HTTP 300 navigation and the "frm" prefix in the destination URL are additional complaints.

### Source excerpt

We still get a fair bit of old school ASP .Net webforms code, which was cutting edge about twenty years ago, but remains a collection of bad choices that tried to make web programming feel like desktop programming. As an aside, what a reversed world we live in today, where everyone uses Electron and our desktop programming feels like web programming. In any case, Thomas sends us some pretty ugly webforms code. Me.Session("Albumid") = CType(e.Item.FindControl("lblAlbumID"), Label).Text If Not Me.Session("Albumid") Is Nothing And Not Me.Session("Uid") Is Nothing Then Me.strDelSQL = "Delete from tbl_Albumshare_Mast where Album_Id=" & Me.Session("Albumid") & " and Sharer_ID=" & Me.Session("Uid") Me.objDB.ExecQry(Me.strDelSQL) Me.Response.Redirect("frmmyalbumshare.aspx", False) End If Broadly, the goal of this code is to take an album ID from the user and delete an album from the database where the ID matches and the album is owned by this user. And everything is horrible here. First, the use of e.Item.FindControl to look up the input field is suspicious. That's usually what you do when you've dynamically generated controls, but I don't think that's happening here. Because we use FindControl we have to cast it to Label, and only then can we get the text property. That itself raises a question, because why are user inputs getting stored in a label?. That's not what labels are for. They're clearly doing some sort of hacky lookup/autocomplete field thing and using the label to actually store the input, but presenting the user with a different UI for picking it. Not an uncommon pattern in those days, but a hidden field would be a more typical way of doing it. We then construct a SQL injection vulnerability and run it against the database. Then, we use a redirect to send the user to a different page. Again, a common thing to do back then, but a thing I hate: using HTTP 300 codes to redirect users as a form of navigation is awkward and weird. Of course, none of that is precise

## News Roundup: Security Fourth

DevFeed: [News Roundup: Security Fourth](<https://devfeed.tech/articles/news-roundup-security-fourth-102728.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/security-fourth>)

Author: Remy Porter

Published: 2026-10-27T06:30:00Z

Content type: news

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>)

Tags: [llm](<https://devfeed.tech/tags/llm.md>), [llm-tools](<https://devfeed.tech/tags/llm-tools.md>), [llms](<https://devfeed.tech/tags/llms.md>), [news](<https://devfeed.tech/tags/news.md>), [news-roundup](<https://devfeed.tech/tags/news-roundup.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [security](<https://devfeed.tech/tags/security.md>), [security-incidents](<https://devfeed.tech/tags/security-incidents.md>)

### AI overview

The excerpt describes two serious security failures. PHP2Shell reportedly affected every PHP version for 20 years: a request-size check bypass can cause an out-of-memory error, while faulty cleanup can enable use-after-free code execution before a request reaches application code. LLM tools helped discover it, but the author attributes their value to processing structured text and running tests, and emphasizes human handling of the embargo. Patches are available for PHP 8.2 and later; source patches extend back to 7.4, which is end-of-life. Separately, an eMudhra in-house key packing tool truncated 8 of 24 generated keys to one byte after validity checks, making them derivable from public keys. The author says no certificates were issued under affected authorities, but others could have used the weak keys, and trust-store cleanup remained incomplete at the time of writing. eMudhra announced it would leave global SSL/TLS, citing business costs and scrutiny.

### Source excerpt

A bit ago, I broke with my usual pattern and wrote up some security issues that I felt were particularly funny. It was a change of pace, a different thing, but not a thing that'd become a habit. After all, I'm not a security expert, this isn't a security site, and seriously, what are the odds that suitably funny security issues would crop up again less than a week later? Well. Let's start with the actual serious issue, PHP2Shell. In terms of scope, every version of PHP for the past twenty years has had this bug. The general issue that permits the exploit was known about, but wasn't considered exploitable. Oops. The broad strokes of the bug is that it's two separate bugs. The first allows someone to bypass the checks on a request's size, thus giving them a direct route to triggering an out-of-memory error. The second is that, depending where you are in the processing pipeline, PHP doesn't properly handle cleanup, allowing for use-after-free that can trigger code execution. It doesn't matter what code you've written, this all happens before the request even hits your code. Bigger oops. This bug was found via LLM tools, which has lead to a lot of hype around the idea that we've entered some new era. I'll certainly grant that the ability to throw compute at hacking challenges instead of human effort is going to shift the landscape, but I'm not quite willing to buy the apocalyptic prophecies. Especially when some of those prophets are telling us that their AIs will avoid deletion by copying themselves onto your thermostat. I think it's safe to say we're going to see a lot of security incidents coming out of LLMs in the near future, not because they're magic genius hackers, but because they're pretty good at processing structured text and running tests. For those of us living in the real world, the concern isn't AIs, but HIs: human intelligences. In this case, the exploit was discovered back in August. Security researchers and the PHP Foundation put their heads down to wo

## Securely Useless

DevFeed: [Securely Useless](<https://devfeed.tech/articles/securely-useless-100974.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/securely-useless>)

Author: Ellis Morning

Published: 2026-10-26T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Software Process](<https://devfeed.tech/topics/software-process.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [bridge](<https://devfeed.tech/tags/bridge.md>), [core](<https://devfeed.tech/tags/core.md>), [feature-articles](<https://devfeed.tech/tags/feature-articles.md>), [it-security](<https://devfeed.tech/tags/it-security.md>), [network](<https://devfeed.tech/tags/network.md>), [security](<https://devfeed.tech/tags/security.md>), [services](<https://devfeed.tech/tags/services.md>), [share](<https://devfeed.tech/tags/share.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [testing](<https://devfeed.tech/tags/testing.md>), [wikis](<https://devfeed.tech/tags/wikis.md>)

### AI overview

A company's strict pursuit of CyberEssentials compliance blocked developers from installing needed tools, connecting across networks, and testing company hardware. The restrictions led to unapproved PCs, improvised network tunnels, and informal IP sharing. The company eventually created a less secure secondary network for development, testing, and internal services, while keeping its official "core" on the high-security network. That core was a share of obsolete, unsearchable documentation; the secondary network grew to about eight times its size and held essential activity. The account illustrates how controls intended to protect the business can impede work and push it into shadow systems.

### Source excerpt

Submitter Chops relates a tale of chasing "The Standard" at any cost: A company had been forced, kicking and screaming, into the 20th century, and then into the 21st. Their range of dumb hardware was no longer being bought by customers who expected at least some way to get the data off it, and a USB stick wouldn't cut it. The techno-fearful hired an external IT company and instructed them to ensure that the company adhered to the UK's "CyberEssentials" programme of IT security. Unfortunately, this meant that the nascent software development capability was immediately hamstrung, as people were denied the right to install and run unapproved software (including software that needed admin level rights in order to work, such as process monitor tools used as standard in software dev and test), could not easily connect across networks (also vital for the software dev), could not add various hardware to the network (such as the company's own products, which made testing them awfully difficult) and so on. A criminal underworld of mystery PCs slowly grew into place, plugging into the network to get things done, disavowed by anyone who saw them. Tunnels grew up, IP addresses were handed round on notepaper (no DNS approvals), a shadow world of software development in the back alleys of the network. Until finally it was too much, and approval was given for a second, less secure network. The plan was that the real core business, the really important parts, they would stay on the high-security side. There would be a second network, with a single bridge, which would serve the various software development and test systems, and also host the myriad new internal services growing up (wikis, servers, tools and so on). This way, the real core business would definitely remain secure, and compliant, and the software side of it and all that would not compromise the heart of the business. The heart of the business ended up being a network share containing a decade of out-of-date, unsearchabl

## Representative Line: Readable Formats

DevFeed: [Representative Line: Readable Formats](<https://devfeed.tech/articles/representative-line-readable-formats-95368.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/readable-formats>)

Author: Remy Porter

Published: 2026-10-22T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [formatting](<https://devfeed.tech/topics/formatting.md>), [concatenation](<https://devfeed.tech/topics/concatenation.md>), [clean-code](<https://devfeed.tech/topics/clean-code.md>)

Tags: [formats](<https://devfeed.tech/tags/formats.md>), [net](<https://devfeed.tech/tags/net.md>), [nuget](<https://devfeed.tech/tags/nuget.md>), [representative-line](<https://devfeed.tech/tags/representative-line.md>)

### AI overview

The excerpt criticizes mixing a .NET numeric format string with concatenation to make decimal places configurable: repeated `new string('0', 2)` fragments obscure the format. It suggests assigning that fragment once to `decimalPlaces` to make the concatenation clearer. It also notes that .NET has a per-mille format specifier and objects to spelling its Unicode symbol as `\u2030` in code. The source presents this as a readability critique, not a broader comparison of formatting approaches.

### Source excerpt

We all love format strings for generating human readable text. Certainly, they're a better choice than string concatenation. Even if I have a blind spot that keeps me from remembering the printf format tokens, I still prefer to use format strings. Jasmine has a co-worker that does use format strings, but they also miss using string concatenation. So they've found a way to combine them, and avoid the perils of making readable code that describes the format of their text. myField.DataFormatString = "{0:#,##0." + new string('0', 2) + ";(#,##0." + new string('0', 2) + ")}"; Now, in their defense, I can see how this code started its life. At some point, they wanted to make the number of decimal places a parameter. And sure, this is an easy way to do that and retain the intent, though this whole thing could be cleaned up with just a simple decimalPlaces = new string('0', 2), which would make the concatenation less confusing to read. Related, while I was checking the documentation on the .NET formatting strings, I learned that they have a per-mille format specifier which requires writing a unicode sigil on most keyboards. I'm sorry, but seeing string perMilleFmt = "#0.## " + '\u2030'; in my code would be TRWTF. [Advertisement] Picking up NuGet is easy. Getting good at it takes time. Download our guide to learn the best practice of NuGet for the Enterprise.

## CodeSOD: Doing the Assignment

DevFeed: [CodeSOD: Doing the Assignment](<https://devfeed.tech/articles/codesod-doing-the-assignment-92580.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/doing-the-assignment>)

Author: Remy Porter

Published: 2026-10-21T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Variable](<https://devfeed.tech/topics/variable.md>)

Tags: [codesod](<https://devfeed.tech/tags/codesod.md>)

### AI overview

The code initializes `x`, `y`, and `z` separately, then chains `x = y = z`, so `x`'s initial value of 3 is overwritten with 4. The excerpt questions why the variables are initialized this way and suggests either assigning 4 to all three in one chain or using a named constant such as `DEFAULT_VALUE` for clarity.

### Source excerpt

Today's code maybe isn't much of a WTF, but it does point in the general direction of, "Damn, you live like this?" Poor Nancy unfortunately does. int x = 3; int y = 4; int z = 4; x = y = z; Each variable is declared and initialized, and then they're set equal to each other. It just raises the question though, why do it this way? Why not declare them and then x = y = z = 4, if we want that? Or maybe, for more clarity, int x = DEFAULT_VALUE; would be more legible, and we can skip the multiple assignments on one line. Why does x get set to 3 but then overwritten? [Advertisement] ProGet's got you covered with security and access controls on your NuGet feeds. Learn more.

## Coveralls outage followed an AWS account shutdown

DevFeed: [Coveralls outage followed an AWS account shutdown](<https://devfeed.tech/articles/the-outage-90637.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/the-outage>)

Author: Remy Porter

Published: 2026-10-20T06:30:00Z

Content type: opinion

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [GCP outage lessons learned](<https://devfeed.tech/topics/gcp-outage-lessons-learned.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [hosting](<https://devfeed.tech/topics/hosting.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [ci](<https://devfeed.tech/tags/ci.md>), [feature-articles](<https://devfeed.tech/tags/feature-articles.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>)

### AI overview

Coveralls' outage caused CI jobs using its code coverage reporting service to fail. The author says AWS shut down the service after mistakenly deciding Coveralls had not paid its bills, and that it took about 68 hours to identify the issue. The piece humorously reads excerpts from Coveralls' outage updates.

### Source excerpt

At my employer, we use a service called Coveralls, which is a code coverage reporting tool that hooks into your CI pipeline. It takes your lcov reports and gives you some insights, and also makes it easy to cause the CI pipeline to fail if newly added code doesn't have reasonable coverage. I have no strong feelings about the tool, but on February 24th, our CI jobs started failing. Coveralls had gone down, and our CI step that talked to them now failed. That happened to us, and a lot of other people. Coveralls actively published updates as the outage dragged on, and boy, did it drag on. Between them posting nearly identical updates minutes or even seconds apart and the general desperation that snuck into their outage notes after the first few days, I couldn't help but find their notes hilarious. They've published their post-mortem, and the short version is that despite them paying their bills, Amazon decided they hadn't, and shut down their services. But it took them roughly 68 hours to figure that out. If you scroll down past the post-mortem, you can see their outage notes. This is an unauthorized, dramatic reading of those notes. We've taken some liberties in interpreting it. I hope this is taken in a good spirit, because they were just doing their best when this happened. I don't think most companies would be able to maintain operations when their cloud provider decides to lock their accounts. But I don't care who you are: begging your users to email you if they can help you migrate off AWS is funny. [Advertisement] Utilize BuildMaster to release your software with confidence, at the pace your business demands. Download today!

## Weak Password Security in Denmark's CPR System

DevFeed: [Weak Password Security in Denmark's CPR System](<https://devfeed.tech/articles/the-frist-line-of-defense-87624.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/the-frist-line-of-defense>)

Author: Remy Porter

Published: 2026-10-15T06:30:00Z

Content type: opinion

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Cybercrime](<https://devfeed.tech/topics/cybercrime.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [blockchain](<https://devfeed.tech/tags/blockchain.md>), [breach](<https://devfeed.tech/tags/breach.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [feature-articles](<https://devfeed.tech/tags/feature-articles.md>)

### AI overview

The author examines a reported breach of Denmark's CPR system involving a third-party account protected by the password 123456, criticizing weak password controls and reliance on identification numbers as secrets. The article also describes alleged hardware tampering involving Ledger wallets and argues that security places too much responsibility on end users.

### Source excerpt

We don't cover a lot of security issues here, simply because they're not usually funny. But sometimes, they are. So here's a quick hit about some recent ones. We start with a very bad month for the Danish social security system, the Central Register of Persons (CPR). Last week, they detected a breach which exposed the personal details of 8.8m people. Per the Register article, a cybersecurity specialist correctly pointed out that treating your ID number as if it were a secret was a terrible idea in the first place, but unfortunately, so many systems have grown up around the idea that full knowledge of your state issued ID number as proof of identity, that the security expert is screaming into the wind. They're right, but it's going to take a lot to change. Okay, Denmark's social security service was hacked. What's so funny about that? Well, the mechanism of the hack appears to go thusly. First, third party companies have access to the database, which they can use to send notifications to their customers via CPR. That connection is secured with a password, and one of those third parties secured their account with the kind of password you'd use to protect the precious air of the planet Arboria. Also known as the kind of password some idiot would put on their luggage: "123456". (paywalled, Danish article). The hacker accessed the system on September 10th, and spent ten days searching through the system. The intrusion wasn't detected until October 2nd, when CPR went to send an invoice to the third party company and noticed, "Boy, that's more searches than they have customers." Now, obviously, CPR should have never even allowed such a low complexity password, but also, the third party company shouldn't have used such a low security password. Now, if you'll excuse me, I have to change the combination on my luggage. In other news, I'm not particularly fond of blockchain stuff. Mostly, the whole distributed ledger seems like a solution in search of problems, and "trading tok

## Representative Line: A Diamond in the Rough

DevFeed: [Representative Line: A Diamond in the Rough](<https://devfeed.tech/articles/representative-line-a-diamond-in-the-rough-87231.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/a-diamond-in-the-rough>)

Author: Remy Porter

Published: 2026-10-14T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Inheritance](<https://devfeed.tech/topics/inheritance.md>), [class](<https://devfeed.tech/topics/class.md>), [subclass](<https://devfeed.tech/topics/subclass.md>)

Tags: [classes](<https://devfeed.tech/tags/classes.md>), [inheritance](<https://devfeed.tech/tags/inheritance.md>), [representative-line](<https://devfeed.tech/tags/representative-line.md>)

### AI overview

The article explains C++ virtual inheritance as a way to address the diamond problem, then describes code where using virtual inheritance on a final class has no effect because the class cannot be inherited from.

### Source excerpt

Mandy's co-worker recently learned about virtual inheritance in C++. It's become their new favorite button to push, and they only use virtual inheritance. Virtual inheritance is one workaround for the "diamond problem", where you have an inheritance tree that "recombines" via multiple inheritance: when a child class has a Hapsburg-esque parentage, it's hard to decide which inherited methods are being invoked or overridden. In C++, imagine you have class A, which gets derived into classes B and C. Class D then uses multiple inheritance to inherit from B and C. In practice, this means that D inherits from A twice, and would have two internal copies of all of A's members. If, on the other hand, you have B and C inherit virtually (class B : public virtual A), then class D will only actually inherit a single copy of A. If you're reading this and going, "Boy, this just sounds like another reason to avoid multiple inheritance," you're probably right. The important thing, though, is inheriting virtually impacts how your child classes will inherit. It only matters if you have child classes. Which brings us back to Mandy's co-worker. He read somewhere that defaulting to virtual inheritance all the time was safer, so he did that all the time. All. The. Time. Including in this case: class SomeSpecificDerivedClass final : public virtual SomeBaseClass The class here is marked final. It can't be inherited from. The use of virtual accomplishes nothing. [Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!

## Editor's Soapbox: Digital Mail

DevFeed: [Editor's Soapbox: Digital Mail](<https://devfeed.tech/articles/editor-s-soapbox-digital-mail-85840.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/digital-mail>)

Author: Ellis Morning

Published: 2026-10-13T06:30:00Z

Content type: opinion

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Cybercrime](<https://devfeed.tech/topics/cybercrime.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [editor-s-soapbox](<https://devfeed.tech/tags/editor-s-soapbox.md>), [nonprofit](<https://devfeed.tech/tags/nonprofit.md>), [threat-detection](<https://devfeed.tech/tags/threat-detection.md>)

### AI overview

The author criticizes prison systems that digitize and censor incoming and outgoing mail, charge incarcerated people to view it on tablets, and use AI to flag content. The opinion argues that these practices harm incarcerated people and their connections with family and friends, while states have not shown evidence that the measures achieve their stated drug prevention goal. It urges technology professionals to avoid or challenge work that enables these practices and to raise awareness.

### Source excerpt

Ever get some special letter, card, or picture from a friend or loved one that you held onto, maybe even taped to your cube or office wall? Is it something you still look at fondly, something that lifts your spirits whenever you're down? Certainly, a thoughtful card or letter is much nicer than a thoughtful email. Now imagine your special keepsake being scanned, censored, and converted into a digital file that you can only view from a tablet -- assuming you can afford the fee to access the tablet. The original has been destroyed; it's gone forever. You'll never get to see or feel it in your hands. It sounds almost too cruel, like something you'd find in a Fallout game. Unfortunately, it's reality for more and more people incarcerated in US prisons. I've been writing to an incarcerated person for a while now myself. I find the process incredibly rewarding; I think about my friend all the time and wish them well. Unfortunately, the scanning and processing takes absolutely forever, so in a given year we only exchange 3 letters per side. The digitized files that I receive have names censored out of them; I have no idea what's removed from my letters before my friend receives them. For me, this is all too reminiscent of exchanging letters with my grandmother in Iran before she died. Agents there would straight-up open the envelope, confiscate any valuables inside, marker over anything they didn't like, then re-seal the envelope and send it back on its merry way. Over 30 US states now digitize the mail passing in and out of prisons, relying on AI to judge what's kosher and what isn't. If you thought AI was great with resumes, just wait until you task it with threat detection! It's been working so well that one nonprofit organization had to change its name: the word fight, used in any context whatsoever, gets flagged. Once mail is scanned, it's only accessible by tablets that have to be paid for. Incarcerated people are already nickled and dimed for a ridiculous number of t

## CodeSOD: A Type of Type Safety

DevFeed: [CodeSOD: A Type of Type Safety](<https://devfeed.tech/articles/codesod-a-type-of-type-safety-85187.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/a-type-of-type-safety>)

Author: Remy Porter

Published: 2026-10-12T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Polymorphism](<https://devfeed.tech/topics/polymorphism.md>), [Inheritance](<https://devfeed.tech/topics/inheritance.md>), [typesafety](<https://devfeed.tech/topics/typesafety.md>)

Tags: [c](<https://devfeed.tech/tags/c.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [code](<https://devfeed.tech/tags/code.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [inheritance](<https://devfeed.tech/tags/inheritance.md>), [polymorphism](<https://devfeed.tech/tags/polymorphism.md>), [type-safety](<https://devfeed.tech/tags/type-safety.md>), [type-system](<https://devfeed.tech/tags/type-system.md>)

### AI overview

The article critiques a C++ codebase that uses runtime type checks and casts to restrict behavior based on object types. It explains how this approach misuses C++ casting and contrasts it with using polymorphism and dynamic dispatch to model the domain.

### Source excerpt

For some godawful reason, people like to explain object oriented concepts via analogy to biological taxonomies. I suppose it's easy to understand an "is-a" relationship (a cat is a mammal), but the down side is you get a complex and increasingly leaky analogy that over-emphasizes the importance of inheritance. That's not to slight Alan's choice of using it to anoymize today's code. It's just a broad frustration on my part. In any case, Alan has been working in a C++ codebase that's written by people who maybe don't fully understand all the key object oriented concepts. That's why you get code like this: /* * If possible, steal tentacle from the given animal. */ void Animal::StealTentacle(Animal *animal) { // only Octopus and Squid can have tentacles if (!IS_INSTANCE_OF(this, Octopus) && !IS_INSTANCE_OF(this, Squid)) { return; } Limb *limb = animal->mLimbs->GetFirstTentacle(); if (limb) { limb->AttachToAnimal(this); // . . . This function takes a raw pointer to an Animal object. If that pointer is not an Octopus or a Squid, we bail. Otherwise, we're going to take its tentacle, and do stuff with it. Now, this is a pretty clear example of the type switch anti-pattern. Instead of using the type system and polymorphism to enforce restrictions, we instead do runtime type checks. But wait a second, what's going on in that IS_INSTANCE_OF? // I've noticed that dynamic_cast always returns a valid result when // casting an "objectPointer" of type "className". // Try casting it to a [Organism *] to force it to work. (?) #define IS_INSTANCE_OF(objectPointer, className) ((bool) (dynamic_cast<className *>(((Organism *) objectPointer)) != NULL)) #define IS_MEMBER_OF(objectPointer, className) IS_INSTANCE_OF(objectPointer, className) // temporary macro alias This code attempts to take an objectPointer and first, force it into a pointer to our base type (Organism), using a C-style cast. Now, in C++, C-style casts are a shorthand, and the compiler will, based on the context, attempt to

[Next page](<https://devfeed.tech/sources/the-daily-wtf.md?cursor=WyIyMDI2LTEwLTEyVDA2OjMwOjAwKzAwOjAwIiwgIjkzZmY4MTFjLTMwMDQtNGI5Yi04NTMzLWQ2YTZjY2Y5MGJmMSJd>)