The Daily WTF - TheNote.app

The Daily WTF
Follow

The Daily WTF is a programming-oriented humor blog created by Alex Papadimoulis based on stories about software development and the world of technology. It mainly focuses on anecdotes based on project issues, code examples, and funny stories related to IT. The site contains a vast collection of these real-world experiences by many developers who share their strange and funny encounters at work, both technical or personal, but always connected to related tech.

The Daily WTF thedailywtf.com

RSS feeds.feedburner.com

RSS Hunter • Aug 19, 2024

Thread Of Notes

The Hard Goodbye

The narrator is struggling to cope with the sudden loss of their friend and mentor, Aggie Shaw, who died of a sudden illness. The narrator is overwhelmed with grief and finds it impossible to return to work as usual, despite their boss's expectations. They start using their paid time off to deal with their emotions and try to come to terms with the loss. The narrator's friend Megan reaches out and offers to meet up, providing a much-needed listening ear and a sense of comfort. During their meeting, the narrator opens up about their feelings and frustrations with their job, and Megan suggests that they could start their own IT group with equal partners. The narrator is inspired by the idea and starts to explore options, including going freelance and starting a new business with Megan. As they research and plan, they find a sense of purpose and excitement, despite the risks and uncertainties. The narrator returns to work, but only to give their two-week notice and start making plans for a new future. They find a symbol of Aggie's presence, a rubber duck, in her old office, which gives them a sense of connection and motivation to move forward. The narrator is determined to leave their old job behind and start a new chapter in their life, with Megan by their side. The narrator's decision to leave their job is not just about escaping a difficult work environment, but about finding a new sense of purpose and fulfillment.

https://thedailywtf.com/articles/the-hard-goodbye thedailywtf.com

RSS Hunter • Yesterday

Error'd: The Song that Never Ends?

Scammers insist on users watching content to the end, a task humorously presented as a long-term commitment in today's "Error'd" episode. Amazon recently generated widespread concern by sending out significantly overpriced bills to thousands of customers, causing considerable alarm. One customer, Willy, expressed worry over the sudden increase in Amazon prices and anticipated financial scrutiny. Dave A. highlighted a software prompt's indecisiveness, questioning whether an action was optional or required. An anonymous user discovered a unique 5-star rating system displayed on both X and Y axes for a roof-cleaning company, humorously noting it was "out of the roof." Richard H. encountered a suspicious QuickBooks email referencing a randomly generated invoice number, strongly suggesting it was a scam. B.J. H. received an unusually verbose and alarming system message, raising concerns about emergency protocols if such text was considered "normal." The episode also included an advertisement for a guide on migrating to .NET 9, promising to alleviate migration difficulties.

https://thedailywtf.com/articles/the-song-that-never-ends thedailywtf.com

RSS Hunter • Jul 24

Classic WTF: My Many Girlfriends

Remy humorously suggests retreating to a dark, unventilated cave due to unpleasant weather. This sentiment echoes a past workplace dynamic where managers tolerated eccentric software developers. In the late 90s, with the IT boom, managers were accustomed to unusual behavior from their developers. When hiring Sten, who had glowing recommendations, Barry and his team prepared for eccentricity.On his first day, Sten requested a workspace with no natural light and closable ventilation. Barry discovered Sten's office in the basement, where Sten was removing fluorescent bulbs to darken the space. Sten spoke exclusively in the third person, referring to himself as "Sten" and using pronouns in a confusing manner. He also consumed large amounts of vitamins and a peculiar-smelling tea.Sten's coding style was equally peculiar, using female first names for all variables and methods, named after his supposed girlfriends. While some naming conventions existed, they were undocumented and difficult to decipher. Code reviews became elaborate narratives, making it hard to understand the actual logic.Despite his eccentricities and coding style, Sten's primary downfall was his slow productivity. He couldn't keep pace with the team's demands, leading to his termination. Barry later provided a cautious reference to another company, suggesting they have Sten explain his code. Sten was not hired by that company, and Barry received a thank-you gift basket.

https://thedailywtf.com/articles/classic-wtf-my-many-girlfriends thedailywtf.com

RSS Hunter • Jul 23

Classic WTF: Server Room Fans and More Fun

Technicians face recurring challenges with poorly maintained infrastructure and unconventional solutions. One common issue arises from an underpowered air conditioner, prompting a warning to watch for trip hazards near an open server room door. Another technician struggled with a fax machine that only worked sporadically in wet weather, despite extensive troubleshooting and line testing. The problem was eventually traced to an exposed telco vault where cables were left unprotected, leading to a prompt fix after photographic evidence was sent to management.Another unsettling discovery involved an "off-site backup" drive haphazardly placed on a wooden server rack within a software company. Further examples of makeshift solutions include the use of unconventional wiring that deviates from standard electrical practices, preferring exposed connections over proper installations. A hotel in Manhattan revealed its network equipment hanging precariously from cables in a public stairwell, completely unsecured. In China, a switch was found bolted several meters high to a column in a metal shop, highlighting more unusual installations in industrial settings.These incidents underscore a pervasive lack of professional standards in IT infrastructure management across various environments. They suggest a pattern of improvisation and neglect rather than adherence to best practices.

https://thedailywtf.com/articles/classic-wtf-server-room-fans-and-more-fun thedailywtf.com

RSS Hunter • Jul 22

CodeSOD: Classic WTF: Fork and Log

Remy recounts an incident involving a VXML Platform performance issue encountered by Adam C. The system was failing under minimal load, and the project was already behind schedule. Adam, unfamiliar with VXML, began by examining application logs for clues. He repeatedly found an error message stating "Exception encountered writing error log." This cryptic message puzzled Adam, as it reported an error in logging itself. Delving into the source code, he discovered a deeply flawed logging implementation. The code used an external command to log errors, rather than leveraging existing logging frameworks like log4j or even a simple System.out.println. Adam found this approach inefficient and poorly designed. Although this specific code was not the root cause of the performance issues, it was quickly removed. The anecdote highlights a common type of technical debt found in legacy systems.

https://thedailywtf.com/articles/classic-wtf-fork-and-log thedailywtf.com

RSS Hunter • Jul 21

CodeSOD: Classic WTF: The Table Selector

The article revisits classic code examples during summer break, starting with a discussion of source code. The author, Christian, notes that in German, "quellcode" directly translates to "source code." He humorously coins a new term, "quäl-kot," which combines a German expletive with "source code," to describe particularly egregious code. This evocative term is inspired by a poorly designed interface encountered in the codebase.The problematic interface is presented as a C# code snippet. It is named ITableSelector and contains an excessive number of methods for selecting tables. Specifically, it has methods like selectTable1(), selectTable2(), and numerous variants for tables like 4a/4b, 7a/7b, 9a/9b, 14a/14b/14c/14d, and 21a/21b. The interface continues to list methods all the way up to selectTable31(). This extensive and repetitive list highlights the interface's design flaws. The sheer volume of similar methods indicates a lack of abstraction or a poorly structured solution. Such an interface suggests potential problems with maintainability and extensibility.

https://thedailywtf.com/articles/classic-wtf-the-table-selector thedailywtf.com

RSS Hunter • Jul 20

Error'd: Princess Pricing

Sam speculates Disney+ might be testing usage-based billing due to an error. However, a more common explanation is likely. An online shopping site displayed illogical pricing, offering a discount on an item with a price of zero. Harrison observed a supermarket item marked with a reverse price change, showing zero as the original price and 99 dollars as the new price. The discount was paradoxically described as negative infinity percent. Dragoncoder047 encountered mojibake on their iPhone's Game Center widget despite the device being set to English. Evelyn reported a package tracking anomaly where an item was registered in July, shipped in January, and then returned to July. This timeline inconsistency is not attributed to simple time zone issues. These examples highlight various online and real-world glitches. The errors range from billing possibilities to pricing absurdities and display mishaps. They showcase unexpected digital and logistical anomalies encountered by users.

https://thedailywtf.com/articles/princess-pricing thedailywtf.com

RSS Hunter • Jul 17

CodeSOD: Wait Longer

Karen encountered flakiness in her specification tests, occurring a few times per thousand runs. These complex, timing-sensitive tests failed occasionally despite generous timing windows and passing unit tests. The issue stemmed from JavaScript's setTimeout, which, unlike its documentation suggesting it may wait longer, can actually invoke callbacks before the specified time elapses in Node.js. Karen's simple wait function initially used setTimeout to introduce delays. After extensive debugging, she discovered this timing inconsistency was the root cause of her flaky tests. To resolve this, she rewrote the wait function to continuously check the elapsed time every millisecond. This new function ensures the operation completes only after the target duration has been met, preventing premature timeouts. While effective, this solution is considered inefficient and highlights the problematic time sensitivity of functional tests. It also points to a deficiency in the Node.js runtime's scheduling guarantees. The author expresses dismay that such a workaround is necessary.

https://thedailywtf.com/articles/wait-longer thedailywtf.com

RSS Hunter • Jul 16

CodeSOD: The Error Check

The codebase is primarily written in C, where function return values typically indicate status codes. The standard convention is to check if a boolean return value is true for success. However, a long-time developer introduced a confusing alternative idiom. This developer checks if the boolean return value is false to signify an error. This practice has become the prevailing convention within the project due to the developer's tenure. Consequently, any potential error condition involves checking if a variable named 'error' is equal to FALSE. While consistent within its own framework, this convention is not formally documented. New developers often initially adhere to the standard pattern. However, the sheer volume of existing code with the non-standard pattern influences them. This established codebase possesses a strong inertia that shapes new code. The existing code effectively dictates the development style, rather than developers altering the code.

https://thedailywtf.com/articles/the-error-check thedailywtf.com

RSS Hunter • Jul 15

CodeSOD: AAYFN

The provided Ruby code defines a function named bv, which is short for boolean value, and is used to pretty-print boolean values and convert them to strings. The function takes four parameters: prop, tv, fv, and nv, which represent the property name, true value, false value, and null value respectively. The function uses the send method to access a member of the class by name, which is a Ruby idiom that allows for metaprogramming by strings. This approach can lead to potential issues, such as returning "Not Specified" for non-boolean fields, which can be misleading. It is argued that attempting to use the function on a non-boolean field should throw an exception instead. The function's behavior can be surprising, as it will throw an exception if the property does not exist or if the thing being accessed is a function that takes parameters. The Ruby documentation recommends having a good list of allowed boolean values to avoid these issues. However, the use of runtime metaprogramming by passing strings around can still lead to trouble and make the codebase difficult to maintain. The author of the text expresses their dislike for this approach and prefers using C++ templates for metaprogramming, which they find to be simpler and clearer. The author believes that non-trivial Ruby codebases often become unmaintainable due to the use of metaprogramming. Overall, the code and its approach are considered to be problematic and prone to errors.

https://thedailywtf.com/articles/aayfn thedailywtf.com

RSS Hunter • Jul 14

The Easy No

The narrator, Anonymous, recounts their experience troubleshooting a printer issue in Human Resources. Print jobs were being misdirected, causing strange output, and the culprit was suspected to be an outdated, undocumented HR program. The narrator and their colleague Reynaldo discovered an IP address conflict where the printer shared an address with a decommissioned server still inexplicably running. Reynaldo theorized this server was caching and printing old, anonymous complaints from the forgotten program. Developer Megan provided the program's source code, confirming it was an undocumented mess created by a retired developer. Megan offered to improve the program's error handling, but her boss interrupted, forbidding her from working on unsupported projects. Frustrated by corporate bureaucracy, Anonymous escalated concerns to the new head of HR via email. Meanwhile, Anonymous arranged a meeting with their mentor, Aggie, to discuss the systemic issues plaguing the company. Tragically, Aggie passed away unexpectedly from a heart attack before their meeting could occur. The narrator was left with unresolved frustrations about the company's inefficiencies and the loss of a valued mentor.

https://thedailywtf.com/articles/the-easy-no thedailywtf.com

RSS Hunter • Jul 13

Error'd: Einfach so

The conversation starts with a discussion about how to pronounce FAQ, with Peter saying it as "eff eh cue". A test is then mentioned, and Peter is asked to create an FAQ with exactly nine entries. An anonymous person mentions spending an unknown amount of money and missing out on an interesting offer on myminifactory.com due to a tight expiry date. Another reader expresses their expectation of speedy delivery, sharing a screenshot and noting the discrepancy between the estimated delivery time and their local time. The reader finds the delay unusual but welcomes the change. Michael R. laments missing out on six coupons that would have saved him 0%, which he finds hurtful. Dragoncoder047 shares their frustrating experience with a game engine, where they encountered an unhelpful error message while refactoring the runtime spritesheet packer. The error message was unclear, and Dragoncoder047 had to figure out the problem, which involved the improper detection of certain elements. The conversation is interrupted by an advertisement for BuildMaster, a software release management tool that allows businesses to release software with confidence and at their desired pace. The advertisement encourages readers to download BuildMaster today to utilize its features and benefits.

https://thedailywtf.com/articles/einfach-so thedailywtf.com

RSS Hunter • Jul 10

Flushed Out

The true value of a project manager lies in their communication skills, not just their planning abilities. Effective project managers bridge the gap between the team, organizational goals, and leadership, while managing constraints. A competent project manager is invaluable, while an ineffective one can be costly. Tegan, a new MBA graduate with certifications but no practical experience, was assigned to lead a complex project. She lacked the essential communication skills needed to effectively manage her team of experienced engineers. When asked for critical timeline information, Tegan provided vague and unhelpful responses. The engineering teams began collaborating directly, bypassing Tegan, which displeased management who relied on her for project insights. Unable to make informed decisions due to her inexperience, Tegan's communication deteriorated, leading to project stagnation. Her eventual email admitting she was "constipated" humorously highlighted her inability to progress. Ultimately, Tegan left the project, and her replacement, Pam, though not exceptional, brought much-needed consistent communication and experience to keep the project moving forward.

https://thedailywtf.com/articles/flushed-out thedailywtf.com

RSS Hunter • Jul 9

CodeSOD: Module Test

TJ inherited a NestJS project with code from developers who have long since departed. NestJS is a TypeScript framework that uses dependency injection. It organizes code into controllers, providers, and modules. Modules can be nested, creating a flexible dependency structure. The ProjectsModule in the codebase is an example of a basic, empty module. Developers often create tests for their code, and a test file for ProjectsModule exists. This test file attempts to instantiate the ProjectsModule. However, the test simply creates an instance of the module, which is not a meaningful test. NestJS modules are essentially containers, and dynamic modules execute code at runtime, not during construction. Therefore, this specific test will always pass without validating any actual functionality. It's considered a non-test that doesn't contribute to code coverage or verify the module's components. Despite its ineffectiveness, TJ notes the presence of tests.

https://thedailywtf.com/articles/module-test thedailywtf.com

RSS Hunter • Jul 8

CodeSOD: On Hold

The application "Dragoncoder" implements a wait time for users, which the author dislikes but acknowledges may have real-world justifications. The core issue lies within the JavaScript code responsible for displaying this wait time. The variable minutes is hardcoded to 12, and the code exhibits peculiar logic for displaying the estimated wait time. Regardless of the actual minutes value, the displayed wait time is consistently "12 minute" or "12 minutes" for most scenarios. Even when the wait time is exactly 60 minutes, it's displayed as "0 hour." The author speculates that the output text is also server-generated, despite the variable being client-side JavaScript. A more efficient and user-friendly approach would be to use template literals to dynamically calculate and display hours and minutes. The author questions the necessity of the wait time feature altogether, suggesting it might be removed if there aren't strong underlying reasons for its existence. The wait time page is cached by the CDN after initial backend rendering. The backend rendering of the minutes variable is also noted as a less-than-ideal data transfer method. The author highlights the lack of pluralization handling as another minor flaw. The code's output for 60 minutes as "0 hour" is sarcastically linked to a famous movie. The author proposes a simpler, more dynamic client-side calculation for the wait time display. Ultimately, the author suggests re-evaluating the need for the wait time feature.

https://thedailywtf.com/articles/on-hold thedailywtf.com

RSS Hunter • Jul 7

Best of…: Classic WTF: Difficult Personality

The author introduces the story by comparing the Declaration of Independence to quitting a job without notice. Steve joins a new company for his first week and struggles with the codebase, needing help from the architect, Bill. Bill is unavailable due to a mandatory Friday company meeting. Steve anticipates the meeting might be informal, like a party, given the company's startup status. However, he recalls his interview focused on time management and dealing with difficult personalities. Steve soon learns the difficult personality is Frank, the boss, who admonishes him for spending time in the break room. Frank is extremely controlling of the developers' time and activities. During a planning meeting, Frank aggressively berates Bill for taking a break. On Thursday, a feature demonstration meeting is derailed by Frank's tirade about Steve's personalized computer desktop. Frank believes developers should not personalize their workstations to ensure anyone can use any computer. By Friday afternoon, Steve is given a mop for cleaning duties, which are Frank's orders. Frank mandates that developers clean the office themselves, distrusting the cleaning crew. This experience leads Steve to seek employment elsewhere, applying Frank's time management lessons by quitting.

https://thedailywtf.com/articles/classic-wtf-difficult-personality thedailywtf.com

RSS Hunter • Jul 6

Error'd: Kaids Hen 2025

Deutsche Bahn is criticized for frequent delays and confusing seat numbering, with one user questioning the stacking of seats. Another traveler encountered a train monitor that failed to display Unicode characters correctly. A typo in an Italian news report about a plane crash amusingly suggested a return to July 19th, 2989, though the article also highlighted the heroic survival of many passengers. In a lighter vein, a modified double-decker DeLorean was photographed, humorously suggesting passengers could arrive before boarding. These incidents collectively highlight peculiar and sometimes frustrating aspects of mass transit experiences. The Deutsche Bahn seat situation presents a baffling arrangement. The malfunctioning train monitor demonstrates a common technical issue. The typo offers a touch of science fiction to a serious event. The modified DeLorean adds a whimsical element to transportation. Overall, the week's transport news offered a mix of bewilderment and amusement.

https://thedailywtf.com/articles/kaids-hen-2025 thedailywtf.com

RSS Hunter • Jul 3

CodeSOD: The Most Dangerous Game

While discussions of bad video game code are rare, they often focus on specialized performance optimizations rather than maintainability issues. A released game, despite being a professional product from a small team, contains a notable config file related to its multiplayer functionality. This config file allows for extensive adjustments to networking parameters.One setting, net_socks_buffer_size, comes with a warning not to change it. Others, like net_max_message_size and net_max_download_frames, require game restarts if modified and must be powers of two. The net_udp_packet_size is set to a large value, with notes on recommended fragment cutoffs and IPv6 requirements. Further settings control UDP packet buffer sizes, including a warning about discarding packets when the receive buffer is full.There's also an option to override operating system recommendations for UDP packet sizes, which could potentially disable networking or crash the game. The decision to disable UDP checksums is presented as an optional, likely unnecessary, feature. Critically, the ability for players to configure these settings implies the potential to launch denial-of-service attacks against other players' network stacks.The config file humorously warns users not to be "a dick" about changing certain parameters. Beyond the networking, a truly alarming setting is sys_ignore_variable_constraints, explicitly labeled as "DANGEROUS AS F*." The author humorously advocates for this dangerous flag to be added to all games and even their own robot software for potentially destructive purposes.

https://thedailywtf.com/articles/the-most-dangerous-game thedailywtf.com

RSS Hunter • Jul 2

Representative Line: A Specific Key

The hardest problem in computer science is naming things, as illustrated by a recent example. A method named handleRSAPrivateKeyGeneration, which explicitly suggests RSA private key generation, was observed. However, this function actually accepts an algorithm as a parameter, allowing for different implementations. In this specific case, it appeared to inject a key for implementation lookup. The function does not exclusively generate RSA keys; it returns a valid cryptographic key. By default, it generates an elliptic curve key. This key is returned as a String, likely for display in a web page as part of a Java Spring controller. The submitter found this not to be a "WTF" but rather a poorly named function that could be misleading. Being too specific in naming can sometimes reduce clarity. A better name, like handlePrivateKeyGeneration, would be more appropriate as the exact key type isn't always known. The challenge of naming accurately and clearly persists.

https://thedailywtf.com/articles/a-specific-key thedailywtf.com

RSS Hunter • Jul 1

The Hot Fix

The narrator, a tech support professional, faces a new challenge: a printer in HR that's "printing gibberish." He learns from Tony, the ticket-holder, that the issue is severe enough to warrant an in-person visit. On his way, he briefly reconnects with Aggie, a former mentor who has since been promoted, scheduling a coffee meeting with her. His destination is HR, a department he normally dreads, but he also thinks of Leila, an executive who previously helped him with a difficult case.Upon arrival, he discovers an older man, Tony's boss, attempting to fix the printer with a hairdryer, risking damage to the machine. The narrator intervenes, unplugging the hairdryer and politely but firmly informing the "Hothead" of the potential harm to the printer. He then instructs Hothead to use another printer and promises to resolve the issue himself, while also planning to inform Leila about the incident.After Hothead leaves, the narrator inspects the printer, finding it surprisingly undamaged and fully functional after a series of test prints. He then meets Tony, who confirms Hothead is his boss and expresses gratitude for the narrator's willingness to report the incident to the new head of HR. Tony clarifies that the printer, though old, is "new over here" to their department.Later, during a smoke break, the narrator recounts the morning's events to his colleagues Megan and Reynaldo, showing them the "gibberish" printouts. These pages contain various anonymous HR complaints, such as "I don't feel safe working with Cheryl" and "John keeps staring at me." Megan suggests it might be a network issue, a theory supported by the fact that test prints work fine.Reynaldo, a network admin, recognizes the nature of the printouts, recalling an old, supposedly decommissioned intranet system for anonymous HR complaints. Realizing that the complaints are being unintentionally printed, Reynaldo decides to trace the IP addresses to investigate the source of the issue. The narrator is ready to assist in solving this unusual tech problem.

https://thedailywtf.com/articles/the-hot-fix thedailywtf.com

RSS Hunter • Jun 30

CodeSOD: Off the Path

File path separators can be a challenge when writing cross-platform software, and not all programming languages have a straightforward API for handling them. Prior to C++ 17, developers had to use preprocessor magic to handle file path separators, often using the Boost suite of libraries. A common solution was to define a pre-processor constant for the path separator using conditional compilation directives. This approach allowed developers to assemble paths in a way that worked across different file path conventions. However, some developers took a wrong approach, such as appending a path separator and then replacing it with the correct one, which led to duplicated and error-prone code. This incorrect approach was often copy-pasted throughout the codebase, resulting in multiple instances of the same flawed logic. The code was not refactored, despite being used by multiple developers, and it still produced incorrect path separators in some cases. Fortunately, modern Windows is forgiving of incorrect path separators, but this does not excuse the poor coding practice. A better approach would be to define a constant for the path separator and use it consistently throughout the codebase. The use of a self-service release management platform, such as BuildMaster, can help streamline the development process and reduce the likelihood of such errors.

https://thedailywtf.com/articles/off-the-path thedailywtf.com

RSS Hunter • Jun 29

Error'd: Fi fa foe

This week's tech news highlights several amusing blunders and frustrations across different platforms. A "fifafail" involved a live TV broadcast of the World Cup where the on-screen text incorrectly displayed country names, despite the host verbally correcting it. Another user, WorkerNumber29200, expressed surprise at a job search engine's sudden "expansion" of France, suggesting a bug in its geographical filtering. GitHub was also a source of amusement, with Hans K. reporting a problematic Dependabot issue he wished he could fix. Peter S. further noted GitHub's apparent difficulty with basic arithmetic, humorously suggesting it might have "an unpublished proof that 0=1." The recent issues on Amazon were also discussed, with Michele frustrated by a search for a USB-C charger yielding expensive, obscure music CDs, possibly AI-generated. The article ends with an advertisement for BuildMaster, a self-service release management platform.

https://thedailywtf.com/articles/fi-fa-foe thedailywtf.com

RSS Hunter • Jun 26

The Roadmap

Gary anticipated praise during a meeting with his managers due to recent project successes. He had inherited a chaotic application with an absurd number of duplicated controllers and a disorganized infrastructure. The system suffered from poor uptime and a manual, unreliable deployment process. The backlog was equally unmanageable, lacking any priorities or clear task descriptions. Gary and his team, however, took initiative to address the critical issues. They significantly reduced cloud costs by eliminating redundant resources and implementing strategic planning. Implementing a CI/CD pipeline streamlined deployments and drastically improved system uptime. Gary was ready to present these achievements, expecting commendation. Instead, his managers expressed concerns about his perceived lack of progress on the outdated roadmap. Despite Gary's explanations of substantial cost savings and improved development cycles, his managers remained fixated on the unaddressed roadmap items. They dismissed his suggestions for roadmap revision as unproductive. Ultimately, Gary ended the meeting feeling unappreciated. This experience led Gary to begin updating his resume, indicating his dissatisfaction.

https://thedailywtf.com/articles/the-roadmap thedailywtf.com

RSS Hunter • Jun 25

CodeSOD: Authorized Logger

Gretchen's development team was acquired by Initech as part of a company purchase. Initech was interested in their successful software products and their development talent. Initially, Gretchen's team was successful, being given autonomy over projects. They could reuse existing code or rewrite it and choose their own tools, leading to positive outcomes. However, Gretchen was later assigned to a troubled project characterized by constant "firefighting." The project's codebase exhibited poor practices, such as inadequate null handling.The application was constrained to an outdated version of NodeJS, which was no longer receiving updates. Gretchen noted a lack of consistent coding conventions and absent logging. Even the existing logging mechanism was ineffective, only printing the word "DEBUG" regardless of the message content. The code handled HTTP requests by inserting the request body directly into the database without validation. This particular function demonstrated indecision by attempting two different methods for copying request data.Furthermore, the system relied on direct SQL queries in many areas, creating significant SQL injection vulnerabilities. The code also lacked crucial authorization checks, with most endpoints completely unprotected. Even critical endpoints like the admin API had duplicate versions without any authentication configured. This situation highlighted a severe deficiency in security and code quality within the project.

https://thedailywtf.com/articles/authorized-logger thedailywtf.com

RSS Hunter • Jun 24

CodeSOD: Do a Lot to Do Nothing

A legacy finance application contains a C# method, ValueAGPFund, which is criticized for its numerous side effects. This method modifies its input parameters and internal class members, performing multiple distinct operations. It also interacts with a method called CheckPreviousValuationIfRequired. This latter method is designed to retrieve and process previous valuation data based on specific parameters.A significant issue arises from a circular dependency where ValueAGPFund calls CheckPreviousValuationIfRequired, which in turn calls ValueAGPFund. Furthermore, the return statement in CheckPreviousValuationIfRequired is flawed, leading to a NullReferenceException when it attempts to access a null value. This error likely masks the intended logic, which was presumably to recursively call ValueAGPFund only when prior valuation data existed. The current implementation means this function either returns null or throws an exception.Despite these apparent flaws, the application reportedly functions correctly. The submitter suspects that the problematic code, CheckPreviousValuationIfRequired and its interaction with ValueAGPFund, might be redundant. However, they are hesitant to remove it without confirming if it has any unforeseen side effects or if other parts of the system rely on the thrown NullReferenceException. The submitter sarcastically notes that unit tests would typically mitigate such risks, implying their absence or inadequacy. The core problem lies in the complex and potentially broken logic of these interdependent methods.

https://thedailywtf.com/articles/do-a-lot-to-do-nothing thedailywtf.com

RSS Hunter • Jun 23

CodeSOD: When False is True

Lillith integrated new tools into a Ruby on Rails API that had a "dry_run" feature. This feature allowed services to calculate changes without applying them. A problem arose because the new tool sent {"dry_run": false} in JSON format, but the service interpreted it as true. This unexpected behavior stemmed from a helper method, param_true?, designed to handle stringy or nil inputs. The method's logic, specifically !param_value, incorrectly evaluated actual boolean false as true. This issue likely went unnoticed until POST/PATCH/PUT requests began sending JSON bodies with boolean values. Previously, GET requests probably only sent string representations of parameters. The method's redundant check of params.key?(param_name) after retrieving the value was also noted as an annoyance. The core problem was the helper method's flawed handling of boolean false values. This caused the dry_run flag to be consistently misidentified. The original design's assumption about parameter types appears to have been the root cause.

https://thedailywtf.com/articles/when-false-is-true thedailywtf.com

RSS Hunter • Jun 22

Error'd: Microbits

Two anonymous contributions highlight amusing uses of numbers. The first playfully uses "42" as a numeric answer when a form requires a number. The second expresses surprise at the SAS website's nanobyte precision for file sizes. Mark R. shares a humorous school policy that aims for complete legal coverage of children's communications. Philipp H. offers a confusing message from a chat system, questioning if it's a philosophical statement or a pun. Michael R. succinctly points out irony without specifying its nature. The text also acknowledges Juneteenth and includes an advertisement for a .NET 9 migration guide. The overall tone is lighthearted, focusing on quirky observations and wordplay. One anonymous contributor's numeric fun fact involved a poorly implemented numeric validation. The other numeric observation concerned the extreme precision of file size reporting.

https://thedailywtf.com/articles/microbits thedailywtf.com

RSS Hunter • Jun 19

Representative Line: Sort This Out

An anonymous submitter is working to fix issues left by a previous consultant. They began by addressing the most critical tickets. After clearing those, they started examining code that wasn't currently problematic but showed potential for future issues. While reviewing JavaScript, they discovered a custom sort function which raised immediate concerns. The first line of this function, obj[x._id.account_id] = x.count_total, was particularly alarming. The code incorrectly accesses an account_id field on what should be a MongoDB unique identifier. This indicates that an arbitrary object is being used as a unique identifier in the database, a practice deemed problematic. Beyond the identifier issue, the purpose of this code within a sorting function is unclear. The line appears to be building an object like {"id0": 5} rather than performing a sort. This situation presents a significant mystery, as the code has not yet caused a failure. The primary questions are why it hasn't broken and what will happen when it eventually does.

https://thedailywtf.com/articles/sort-this-out thedailywtf.com

RSS Hunter • Jun 18

CodeSOD: Weekly Calculated

Progress Advanced Business Language (ABL) is described as verbose and English-like. A developer once needed a date six months in the past but deemed accuracy unnecessary. This approach involved complex logic to achieve the approximate date. The code snippet illustrates this process, starting with the current date. It then invokes a procedure to extract the week number and year. Conditional logic adjusts the week number and potentially the year to represent roughly six months prior. Another procedure converts these adjusted values back into a date. The author notes this is a roundabout method for date arithmetic. Progress ABL actually has a dedicated function, ADD_INTERVAL, for such calculations. Mirjam replaced the entire workaround with a single line using this function. The language also exhibits peculiar date handling, allowing date construction from integers within a vast historical and future range. This range spans from before agriculture to the distant future. The verbose nature and unusual date handling contribute to the "WTF" aspect.

https://thedailywtf.com/articles/weekly-calculated thedailywtf.com

RSS Hunter • Jun 17

CodeSOD: Required Fields

Connecting to another system necessitates authentication through credentials. Lisa's inherited connect function, while intending to enforce credential requirements, incorrectly uses default parameter values. This allows the function to be called without any arguments, even though it will ultimately throw an exception. The primary issue lies not just with the misleading default values but with the debugging nightmare it creates. If a username is omitted, the exception correctly states "username is required." However, if the password is omitted, the same misleading error message "username is required" is displayed. This is factually true but does not address the actual problem, which is the missing password. This flawed error messaging exemplifies the concept of being "not even wrong." The error message is technically correct but completely unhelpful in diagnosing the user's specific issue. A more accurate error message would clearly indicate which credential is missing. This design choice significantly hinders effective debugging and user experience.

https://thedailywtf.com/articles/required-fields thedailywtf.com

RSS Hunter • Jun 16

CodeSOD: Caught a Mistake

Daniel encountered an issue where a database query returned no results despite expecting data. He was using a wrapper function called execute_read for database interactions. This function exhibited several questionable design choices. One problem was the only_one parameter, which altered the return type significantly, unlike dedicated database library functions.Another issue was the use of env.is_production() to determine query timing thresholds, suggesting configuration parameters should handle this instead. The most critical flaw, however, was the broad exception handler. This handler indiscriminately caught all errors, logging them but allowing the function to proceed.Consequently, when Daniel's query had a syntax error, the function caught the exception and returned an empty result set. This masked the actual error, causing Daniel to spend considerable time debugging. He eventually found the error buried in the logs. The author highlighted the danger of such silent failures, especially in production environments where network issues could occur. Returning empty results without clear indication of an error leads to significant confusion and debugging difficulties.

https://thedailywtf.com/articles/caught-a-mistake thedailywtf.com

RSS Hunter • Jun 15

Error'd: No Rush

A reader named Adam R. submitted an item about USPS Informed Delivery, a service that emails mail scans daily. He noted an unusual "None" in the email's subject line, suggesting a programming error. Another reader, Carlos, shared an issue with Mint Mobile's template engine, implying a mistake in their system. Robert F. reported a bizarre Carbonite notification stating backup files would be deleted in over a million days, offering an absurdly long timeframe to reconnect a drive. The Beast in Black commented on Claude Code's use of a word, questioning its meaning and suggesting the slow system might be intentionally honest. Peter S. expressed frustration with Sixt's loyalty program, where reaching "silver" status requires filling out extensive data fields with an unclear benefit compared to higher tiers. The author was distracted by YouTube videos after receiving Adam's submission, delaying the column's completion. The submissions highlight various technical glitches and oddities encountered by users in digital services. These errors range from strange text in notifications to improbable timeframes for critical actions. The author humorously acknowledges the distraction posed by the shared video link.

https://thedailywtf.com/articles/no-rush thedailywtf.com

RSS Hunter • Jun 12

CodeSOD: Dating in Hungarian

The author expresses strong disapproval of Hungarian Notation in code. They highlight examples of its misuse and poor date handling. A specific code snippet uses the variable sCDate2 initialized from a hidden field Hdn_SelectedDate. The prefix s suggests a string, but the variable holds a date, and the CDate2 suffix is unexplained. Another hidden field, Hdn_SelectedShifts, stores time as a double, where 10.5 represents 10:30. This value is then manipulated using DateTime.FromOADate. The author delves into the history of OLE Automation and its peculiar date representation, an offset from December 30th, 1899. This system inherited an Excel bug where 1900 was treated as a leap year. The code then converts the double representing hours into an OADate, extracts the time, and combines it with a date string. The author points out that C#'s AddHours method would have been a simpler solution. Furthermore, the time data was manually encoded as floating-point numbers for a dropdown, rather than using a more conventional format. This convoluted process reinforces the author's general dislike for Hungarian Notation.

https://thedailywtf.com/articles/dating-in-hungarian thedailywtf.com

RSS Hunter • Jun 11

CodeSOD: Delicious Fudge

Stella (previously) sends us a much elided snippet. The original code is several thousand lines contained in a single try block. But the WTF is pretty clear without seeing all of that: try: # the whole business logic without any exception handling except: print("Fudge")They didn't really say fudge of course, but we mostly try to keep profanity off our main page. Mostly. In any case, when your operation fails someplace in the middle and you have no idea where, why, or how: "Oh, fudge!" is the appropriate expression.[Advertisement] ProGet’s got you covered with security and access controls on your NuGet feeds. Learn more.

https://thedailywtf.com/articles/delicious-fudge thedailywtf.com

RSS Hunter • Jun 10

CodeSOD: Driven Development

Developers should be cautious of dogma surrounding methodologies like test-driven or domain-driven development. While domain-driven development (DDD) itself is a sound practice, its principles can be rigidly enforced, leading to negative consequences. The core idea of DDD is to model the business domain in abstract terms, separate from technical details. This allows for more effective and tailored domain logic. However, a team boasting about their adherence to DDD, especially with a flurry of buzzwords, can be a warning sign.An example illustrates this issue: a "domain" class for a CakeSessionRepositoryInterface clearly violates DDD principles. A repository in DDD should abstract data storage for domain objects. It should not handle authentication checks, interact with cookies, manage session information, or be tied to a specific web framework like CakePHP. The provided code snippet, despite its brevity, demonstrates a fundamental misunderstanding and misapplication of DDD. This suggests the team was not truly practicing DDD but rather adhering to a superficial interpretation. The misapplication of DDD highlights the dangers of treating methodologies as rigid dogma.

https://thedailywtf.com/articles/driven-development thedailywtf.com

RSS Hunter • Jun 9

CodeSOD: Check and Check

The provided React code snippet displays admin options based on user authorization. It uses a conditional rendering approach with the logical AND operator. If a user is an administrator or has permission to see results, an "Admin Actions" header is rendered. Following the header, a "Show Results" button is also conditionally displayed. This button appears only if the user meets the same authorization criteria: being an admin or able to see results. The author likens this implementation to a "belts and braces" approach, suggesting redundancy. They believe this duplicated condition does not enhance security or functionality. The code aims to restrict access to sensitive administrative features. However, the repeated checks are flagged as unnecessary or inefficient. The core idea is authorized users see admin-related content, but the implementation is questioned for its repetition.

https://thedailywtf.com/articles/check-and-check thedailywtf.com

RSS Hunter • Jun 8

Error'd: Bridge for Sale

A scammer is attempting to defraud individuals by claiming to be part of a consortium looking to buy Google. The scam involves creating fake LinkedIn profiles and sending emails with fictitious company acquisition offers. The scammer likely requests fees just before the supposed deal closure. One victim humorously points out the scam's flaw, stating they don't even own Google. In another anecdote, someone struggles with complex phone billing cycles. A peculiar software issue is described as a "reverse Y2K bug," where an update requires going back in time. A question about calculating 30% of "NaN" is posed, with the answer being well-defined. Finally, a "lost in translation" error is highlighted where a website fails to provide fallback text in English when the browser language is not recognized. An advertisement for BuildMaster, a release management platform, is also included.

https://thedailywtf.com/articles/bridge-for-sale thedailywtf.com

RSS Hunter • Jun 5

CodeSOD: Build Up

String concatenation for SQL queries is a common source of problems. The author advocates for using a SQL builder API instead of raw SQL strings. This builder constructs a syntax tree that can be rendered into SQL when needed, avoiding the issues of direct string manipulation. While ORMs are also an option, the author views them as leaky abstractions. The team was using Java and followed a rule to use a builder, not SQL strings. However, they used a StringBuilder for construction, which technically fits the definition of a builder. This StringBuilder approach was merely string concatenation with extra steps. The example code demonstrates a StringBuilder used to create a query, but the resulting SQL string was fundamentally incorrect and incomplete for its intended purpose. The fact that this broken code ran in production without immediate detection is a significant concern. It implies that errors were silently ignored, or the flawed output was not critical enough to raise alarms. The author highlights this as a "WTF" moment, emphasizing the lack of robust error handling or validation.

https://thedailywtf.com/articles/build-up thedailywtf.com

RSS Hunter • Jun 4

CodeSOD: Coerce the Truth Out of You

Frank encountered unusual JavaScript code using React's useMemo function. The useMemo hook is typically for optimizing expensive calculations. However, in this instance, it was used to determine authorization, which was a simple check of variable values. The specific code snippet revealed a seemingly illogical condition: session && token && !group === false. The author explains that to be authorized, session, token, and group must all be non-null. A more straightforward approach would be session && token && group or !!(session && token && group). The author questions the negation of group and how it could possibly produce the correct authorization result. They elaborate on JavaScript's && operator behavior, including short-circuiting. They then analyze the provided expression, explaining that null === false evaluates to false. The author expresses disbelief that the code functions as intended, suggesting it might be the result of accidental operator accumulation rather than intelligent design. They speculate it could be LLM-generated code or the product of an unskilled developer, emphasizing the lack of clear intent.

https://thedailywtf.com/articles/coerce-the-truth-out-of-you thedailywtf.com

RSS Hunter • Jun 3

CodeSOD: Blocked the Date

The provided PHP code snippet demonstrates flawed date handling. It begins by defining an array of month names in Russian. The code then enters a loop that processes posts, but it redundantly checks for posts twice. The primary issue lies in how the date is parsed and displayed.The date is retrieved as a string and split into parts using periods. The code attempts to extract the month number by examining the digits of the second date part. It checks if the first digit of the month is '0' and takes the second digit if it is, otherwise it takes the first digit. This extracted single digit is then used as an index into the month array.However, this logic is flawed because it only ever extracts a single character for the month index. For months later in the year, this often results in the index being '1', leading to the incorrect display of "January" regardless of the actual month. The author highlights this as cruel and points out the code's locale specificity.The article suggests that using built-in PHP date functions would be a straightforward fix. A side observation is made about PHP's flexible syntax, allowing for alternative block notations like 'if :' and 'endif', which can lead to a confusing mix of styles within a codebase. The author also notes the potential for mixing different programming paradigms.

https://thedailywtf.com/articles/blocked-the-date thedailywtf.com

RSS Hunter • Jun 2

Let's Be Facebook!

A father recounts his involvement with his sons' IT careers beginning around 2012. His three sons secured jobs at a promising web project with significant VIP backing. They later asked their father to invest in the project, which he did. The project launched late, over budget, and incomplete. The CEO then brought the father in to fix the issues, which he successfully did. During his time there, he discovered bids for the project ranged from $5,000 to higher amounts, with one vendor planning to outsource cheap labor from India. After restoring functionality, the CEO declared the project should be rewritten in PHP, inspired by Facebook's alleged use of the language. A meeting followed to estimate the rewrite duration, with most suggesting only a few weeks. The father, however, provided a realistic estimate of at least seven months. Consequently, he was let go for not being "forward-thinking enough." His sons remained for another year, reporting on the extended PHP rewrite. The author uses this experience to illustrate that the most experienced individuals often provide the most accurate, albeit less popular, time and cost estimates. He then invites others to share their own intergenerational workplace oddities.

https://thedailywtf.com/articles/let-s-be-facebook thedailywtf.com

RSS Hunter • Jun 1

Error'd: Super SEO Strategies

This website consistently attracts blogspam due to a simple typo enabling easy website linking. Michael R. is seeking employment opportunities in the United Kingdom and linked a relevant website. B.J.H. is frustrated by the inaccurate weather reporting on Weather.com, specifically the ambiguous temperature forecasts. Jake W. casually mentions a job opening at Durmstrang without any particular urgency or frustration. Martin K. points out a news article that included a date error related to the Microsoft Denmark CEO's resignation. Totty contributes a series of generic and sarcastic comments to the website. The site's primary function is to host brief, humorous, or critical observations about various topics. An advertisement promotes a free guide for migrating to .NET 9, offering assistance to avoid migration difficulties. The overall tone is lighthearted and conversational, with varied user-submitted content. The user interactions suggest a community of commentators and observers.

https://thedailywtf.com/articles/super-seo-strategies thedailywtf.com

RSS Hunter • May 29

CodeSOD: What Condition is This

The provided code defines a function parametersFilter within a Qt application, likely used for probe design. The function takes a probe type, a position index, and a probe design list as input. It aims to generate a pair of strings, to and from, based on the input parameters. The core logic involves a series of conditional statements that handle various scenarios. These scenarios include checking the value of pos (whether it's -1, 0, or the last element's index), and the length of the probeDesign list. The function also checks the type of the probe part, specifically looking for "stylus" elements. The different branches within the code handle edge cases, such as when the list is empty or contains only one element. The primary purpose of these conditions is to perform bound checking on the list. The majority of the typical operation occurs in the final else statement. The analysis suggests that the original code, as complex as it is, could likely be simplified. The author infers that untodesu's "two-liner" suggests a simpler version of the function is possible, possibly streamlining redundant edge-case handling. The code's structure indicates that the original developer may have over-engineered the function to address specific edge cases. The function's complexity stems from the need to handle different positions and probe types within the provided list. Advertisement for a software release tool is also provided within the text.

https://thedailywtf.com/articles/what-condition-is-this thedailywtf.com

RSS Hunter • May 28

CodeSOD: Are There Files Yet?

The text discusses a problematic code snippet from an old PHP ecommerce application. The original developer frequently asked if there were files to send. The presented code aims to attach files to an email if the $files array is populated. The code redundantly checks if the $files array has elements. It then iterates through the array, adding each file as an attachment. The author implies the developer knew the double conditional was unnecessary. The indentation suggests a subconscious awareness of the code's flaws. The critical issue is the redundant condition blocks the application's performance. The simplified approach would involve directly iterating over the files array. The unnecessary conditionals show poor coding practices and lack of understanding. The text concludes with an advertisement for BuildMaster software.

https://thedailywtf.com/articles/are-there-files-yet thedailywtf.com

RSS Hunter • May 27

Whales Ahoy!

The provided text showcases three different experiences of challenging work environments. The first story details an anonymous developer's experience where a client's minor issue of a spinning refresh icon became a top priority, demanding a weekend of unpaid overtime. Their company's focus was dictated by the CEO's importance, highlighting the frustrating prioritization based on client power. The second story, by Daniel Orner, describes a company using "spit and duct tape" to continuously create dynamic digital flyers for a major retailer. This inadequate solution proved functional for eight years, consuming a significant portion of their processing power.The final story, by Brian, illustrates a toxic work environment within the military-industrial complex. Brian's life was dictated more by a massive corporation than his actual needs. He faced constant pressure, demanding work shifts, and a lack of respect following a project takeover. This experience led to a negative perception of the industry, despite offers for future employment. The examples are aimed toward highlighting how difficult some work environments can be. The text concludes with a call for readers to submit their similar experiences and an advertisement for ProGet.

https://thedailywtf.com/articles/whales-ahoy thedailywtf.com

RSS Hunter • May 26

CodeSOD: Classic WTF: One-and-a-Half-Tiered Application Design

The text describes a situation involving a web application with vulnerable JavaScript code. The code, examined by Môshe, used dynamic SQL generation, creating a significant security risk. The sendLinkVal function, meant for handling delivery data, was built with concatenated SQL strings. This allowed for potential SQL injection attacks, exposing sensitive customer data. Môshe discovered this vulnerability, detailing how he was able to manipulate customer data. He reported the issue to the delivery service, leading to contact with the developer. The developer moved the queries to the .NET backend as a solution. However, the backend solution still used concatenated SQL strings. Despite the changes, the application remained susceptible to SQL injection attacks, due to a lack of parameterized queries. The text serves as a cautionary tale of bad programming practices and security flaws.

https://thedailywtf.com/articles/classic-wtf-one-and-a-half-tiered-application-design thedailywtf.com

RSS Hunter • May 25

Error'd: April is Special, and so are you

The blog post celebrates that every month, like April, is special on the website, followed by various humorous observations. One post notes a time discrepancy in Lithuania, suggesting a different time zone or a restaurant error. Another commenter satirizes Amazon's inconsistent shipping estimates, while another offers a pun to conclude the post. Finally, the post is followed by an advertisement for ProGet, focusing on restricting access to NuGet feeds.

https://thedailywtf.com/articles/april-is-special-and-so-are-you thedailywtf.com

RSS Hunter • May 22

CodeSOD: In the Know

Delilah critiques a Python script she found in her workplace. The script attempts to merge YAML data, effectively updating old configurations with new ones. A major problem is the function key_exists, which needlessly recreates Python's built-in in operator. This function uses try-except blocks, a clumsy approach compared to the simple key in dictionary idiom. The script's author inconsistently uses both the correct in operator and the flawed key_exists function within the same code. The code's overall structure is messy, resembling poorly written shell scripting. The script reads and loads YAML files using yaml.load and then merges the data. It contains a revert_db_tags function meant for handling database tag updates. The core logic involves comparing keys and values between the old and new YAML data. The comparisons trigger merging or specific tag adjustments to the new data. Finally, the modified data is written back to the new YAML file using yaml.dump. The author concludes that the script is poorly written and demonstrates an unnecessary complication of Python's built-in functionalities.

https://thedailywtf.com/articles/in-the-know thedailywtf.com

RSS Hunter • May 21

CodeSOD: Find a Bar for This One

The text critiques a poorly designed "data pump" application used to synchronize data between Foo and Bar entities. The application involves a nightly batch job written in Quarkus and interacting with a legacy system. The primary function of the batch job is to identify and update Bar entities based on Foo entities. The code retrieves all Foo entities instead of filtering for missing Bar entities, which is inefficient. The core issue lies in the update process within a transaction that makes multiple web service calls. This design leads to performance problems, including time-outs, contention, and exhaustion of database connections. The use of long-lived transactions, the number of web service calls, and the lack of proper connection pool configuration all contribute to these issues. The author criticizes the necessity of manually managing transactions and the flakiness of the web service. The fundamental problem is the batch job approach itself, which leads to creating referentially unsound data. The author indicates that a redesign will eliminate the batch job altogether, improving the situation. The text concludes with an advertisement for a package management platform.

https://thedailywtf.com/articles/find-a-bar-for-this-one thedailywtf.com

RSS Hunter • May 20

Three Digit Acronyms

JB's database includes a table named three_alpha_numerics designed for generating unique IDs. This table has two columns: digit storing three-character strings and is_numeric indicating if the digit is numeric ('Y') or not ('N'). The primary purpose of this table is to facilitate efficient unique ID generation. A stored procedure utilizes this table to generate unique IDs by joining it with another table and filtering for unused digits. However, the stored procedure only considers rows where is_numeric is 'Y'. Consequently, a significant portion of the table containing non-numeric data is never utilized. The table allows for the generation of a limited set of unique IDs, approximately 1,000, which is deemed sufficient. This design sacrifices the use of a lot of information to generate these IDs. Such a setup is crucial for managing the complex task of generating unique IDs in a database. The unused alphanumeric triplets represent a consequence of this approach. The design prioritizes the generation of unique numeric identifiers, even with the inefficiency. The text then includes a promotional advertisement for BuildMaster.

https://thedailywtf.com/articles/three-digit-acronyms thedailywtf.com

RSS Hunter • May 19