Redundant code Memes

Everyone Is Like This I Think

2 months ago 1.7M views 0 shares

You know that feeling when you write a comment that's so obvious it actually makes the code less clear? Yeah, we've all been there. "The patio is currently not open because it is closed" is the spiritual equivalent of writing // increment i by 1 above i++ . The real tragedy is that whoever wrote that sign probably felt productive doing it. Same energy as when you're trying to hit those "lines of code" metrics and start adding comments like // setting variable to true followed by isOpen = true; We write comments to explain the "why," not to narrate what's already painfully obvious. But hey, at least they documented something, which is more than most codebases can say.

This Is The Explanation

Programming

2 months ago 8.4M views 0 shares

You know those comments that are supposed to explain what the code does? Yeah, they're about as helpful as naming your game "Counter-Strike" and then commenting it with... "Counter-Strike." Zero context, zero explanation, just pure redundancy wrapped in a bow. It's the programming equivalent of asking someone "What's your name?" and they respond with their name. Technically correct? Sure. Useful? Absolutely not. We've all seen (or written, let's be honest) comments like // increment i above i++ or // get user above getUser() . The code literally says what it does already, my friend. Good comments explain the why , not the what . They should tell you about the business logic, the edge cases, or why you chose that weird workaround at 2 AM. Not just restate what anyone with eyes can already see.

It Pays To Double Check They Say

Debugging Gamedev Programming

3 months ago 25.2M views 0 shares

Setting HP to 1, then checking if HP equals 0 approximately 47 times in a row. It's like the developer had trust issues with their own assignment operator. Either they copy-pasted this death sequence from different scenarios and never refactored, or they're coding defensively against some cosmic ray that might flip a bit between line 8 and line 11. The real kicker? Line 13 is highlighted—probably where a bug was found. Imagine debugging this spaghetti and realizing the issue wasn't even in the logic, just buried under an avalanche of redundant conditionals. GameMaker code at its finest: when you're so deep in the game jam crunch that you forget HP was literally set to 1 three microseconds ago.

No, You Don't Understand. What If HP Changed While I Wasn't Looking?

Gamedev Programming Debugging Unity

3 months ago 31.3M views 0 shares

No, You Don't Understand. What If HP Changed While I Wasn't Looking?

Someone set HP to 1 on line 8, then proceeded to check if it's 0 approximately 47 times in a row. Because clearly, HP might spontaneously combust between line 12 and line 15. Or maybe a cosmic ray will flip that bit. Or perhaps the compiler has trust issues. This is what happens when you don't trust your own variables. It's like checking if your car is still locked every 30 seconds in the parking lot. Buddy, you set it to 1. It's not going anywhere. The variable isn't going to get up and change itself while you're calling sound_fix() and creating blood emitters. Pretty sure this code was written during a debugging session that went on for too long, where the developer kept adding "just one more check" until they ended up with this beautiful monument to paranoia. Store HP in a const next time, maybe?

VILVA 15.6" FHD IPS USB-C HDMI Portable Monitor

Affiliate Monitors

VILVA

Experience Unrivaled Visuals: Get the ultimate viewing experience with the VILVA Professional Portable Monitor! With its incredibly sharp 15.6 inch FHD IPS Screen, you'll get a 1920 x 1080 resolution…

If 1: Return True

Programming Python Javascript

7 months ago 424.9K views 1 shares

Oh sweet baby Jesus, the AUDACITY of computers treating the number 1 like it's the holy grail of truth! The computer's sitting there having a full-on religious experience because someone wrote if (1) return true instead of just... returning true. Like, bestie, you're literally checking if 1 is truthy and then returning true. That's not logic, that's a tautology having an identity crisis! It's the programming equivalent of asking "if water is wet, confirm that yes is affirmative." The computer's mind is BLOWN by this completely redundant statement that adds zero value but technically works. Why use one word when you can use five to say the exact same thing? Chef's kiss for unnecessary verbosity! 💋👌

True Or True

Javascript Programming Debugging

7 months ago 514.1K views 0 shares

When you need to make absolutely sure something is true, so you just... set it to true in both branches. The classic "I've covered all my bases" approach that covers absolutely nothing. Either the data exists and we're setting trueOrFalse to true, or it doesn't exist and we're setting trueOrFalse to true. Bulletproof logic right there. This is the programming equivalent of those "choose your own adventure" books where every path leads to the same ending. Just skip the if-else and assign it directly, my friend. Your code reviewer is going to have a field day with this one.

Very Clean Code

Programming Debugging Javascript Typescript

1 year ago 423.1K views 0 shares

THE AUDACITY! This code is checking if a user is NOT null, then returning the user... but if the user IS null, it returns null?! WHAT IS EVEN THE POINT?! 💀 It's like putting on a raincoat during a thunderstorm then immediately jumping into a swimming pool. The entire if-statement is so gloriously redundant it deserves its own monument in the Hall of Fame of Unnecessary Code. This is what happens when you're paid by the line instead of functionality. Chef's kiss of inefficiency! Just write return user and call it a day, PLEASE!

The Redundancy Department Of Redundancy

Debugging Programming Backend Devops Cloud

1 year ago 383.4K views 0 shares

Behold, the classic "belt and suspenders" approach to software engineering! Someone decided to publish that config data twice—once inside the conditional and once outside—because why risk it only being published once, right? This is like ordering pizza, then immediately ordering the exact same pizza again just in case the first one doesn't arrive. The second call will always execute regardless of the condition, making the entire if-statement completely pointless. Somewhere in a code review, a senior developer is quietly dying inside.

Advanced Python Boilerplate

Python Programming Git

1 year ago 431.7K views 0 shares

OH. MY. GOD. Behold the pinnacle of software engineering! Two whole lines of code that redefine variables to... exactly what they already are! 🤦‍♀️ This "ultimate python boilerplate" is the equivalent of telling someone "water is wet" and expecting a Nobel Prize. The sheer audacity of creating a repo for this masterpiece of redundancy! And it's 26 whole bytes! Such efficiency! Such innovation! I'm absolutely DYING at how this captures the essence of those GitHub repos that promise revolutionary code but deliver the programming equivalent of a ham sandwich without the ham.

Context In Comments

Typescript Javascript Programming Debugging

1 year ago 476.4K views 0 shares

Ah, the classic "I'll fix it later" comment that's been sitting there since 2019. The code has an if-else statement that does exactly the same thing in both branches. Someone probably spent hours debugging why their overloaded function wasn't working, then just gave up and wrote this abomination with a promise to fix it "when TypeScript understands overloading well enough." Spoiler alert: they never fixed it, and three devs have since quit rather than touch this cursed file.

NordVPN

Captain Obvious: The Code Commenter

Programming Debugging

1 year ago 273.5K views 0 shares

The AUDACITY of these code comments! A stop sign with another sign below it saying "THIS IS A STOP SIGN" is the PERFECT representation of those mind-numbingly obvious code comments we're forced to endure! You know the ones: // This is a loop right above a FOR loop, or // Function to add numbers above a function literally called addNumbers(). GASP! The horror! It's like someone thought we all collectively lost our ability to recognize basic syntax! Next thing you know, they'll be adding comments like // This code exists just to make absolutely sure we're aware of that groundbreaking fact! 🙄

There Has To Be A Reason Why This Happens

Programming Debugging C++ Algorithms

1 year ago 333.8K views 0 shares

There Has To Be A Reason Why This Happens

The quantum uncertainty principle of code quality! When no one's watching, your code is a beautiful disaster of pointer arithmetic, bit shifting, and variables named "threehalfs" (probably implementing some obscure optimization hack). But the MILLISECOND someone glances at your screen, your code transforms into the most redundant, self-explanatory conditional statement in existence—literally checking if something is true to return true. It's like your code has performance anxiety and suddenly pretends to be following best practices. The compiler doesn't judge you, but that coworker walking by sure does!

Browse