Bad practices Memes

Mock Frontend Newbie Jobs

3 days ago 274.7K views 0 shares

Junior dev discovers Jest mocking and suddenly thinks they're a testing god because they made 2+3=5 pass by... mocking the math module. Yeah, let's just mock away the entire function we're supposed to be testing. What's next, mocking the test itself? This is peak "I wrote tests" energy without understanding that mocking add to return 5 when testing if add(2, 3) equals 5 is like bringing your own answer key to an exam. You're not testing your code, you're just... lying to yourself with extra steps. The hiring manager looking at this portfolio is having a Dipper Pines moment realizing this "100% test coverage" is completely worthless. But hey, at least the tests are green! 🎉

Turns Out, If You Want To Check Multiple Conditions, You Can Sugar It Like This:

Python Programming Debugging

4 days ago 172.3K views 0 shares

Turns Out, If You Want To Check Multiple Conditions, You Can Sugar It Like This:

Behold, the galaxy brain move of creating an array of boolean conditions just to check if ANY of them are false by using .has(false) ! Because apparently writing if (!condition1 || !condition2 || ...) was just TOO readable and maintainable. Someone really woke up and chose violence against code clarity. This is the programming equivalent of using a flamethrower to light a candle – technically it works, but literally everyone watching is horrified. The double negative with return not conditions.has(false) is just *chef's kiss* – maximum confusion achieved! Future developers debugging this will need therapy.

Finish Sprint Faster

Agile Programming Debugging

4 days ago 184.5K views 0 shares

Behold, the ancient art of sprint velocity optimization through strategic negligence! Someone just discovered the SECRET CHEAT CODE to finishing sprints at lightning speed: simply don't document ANYTHING and claim your variable names like "handleData()" and "doStuff()" are "self-explanatory." Sure, your future self will be sitting there six months later staring at a function called "processThings()" that somehow manipulates user permissions, sends emails, AND updates the database, wondering what demon possessed you. But hey, at least you hit that sprint goal and got your little green checkmark in Jira, right? RIGHT?! The sinister handshake says it all—two developers forming an unholy alliance to sacrifice code maintainability at the altar of velocity metrics. Your tech lead is gonna LOVE debugging this masterpiece at 3 AM when production breaks. 🔥

Peak Html

Webdev Frontend

6 days ago 256.1K views 0 shares

Someone really said "screw semantic HTML" and went straight for id="Head" and id="Body" like they're recreating the human anatomy in markup. The irony here is chef's kiss—you've got the actual <head> and <body> tags doing their job, but this developer decided to cosplay them with IDs. It's like naming your dog "Dog" and your cat "Cat" while they already have perfectly good names. Extra points for the redundancy—why use semantic HTML when you can just... label everything explicitly? This is what happens when you take "self-documenting code" way too literally.

When Test Fails Then Fix The Test

Testing Programming Debugging

7 days ago 229.2K views 0 shares

Test-Driven Development? More like Test-Adjusted Development. Why spend 30 minutes debugging your code when you can spend 30 seconds lowering your expectations? Just change that assertEquals(5, result) to assertEquals(result, result) and boom—100% pass rate. Your CI/CD pipeline is green, your manager is happy, and the production bugs? That's Future You's problem. The test isn't wrong if you redefine what "correct" means.

Ffs Plz Could You Just Use Normal Not Equal

Programming

7 days ago 176.6K views 0 shares

Ffs Plz Could You Just Use Normal Not Equal

Look, XOR technically works for inequality checks since it returns true when operands differ, but you're not writing a cryptography library here, buddy. Using a ^ b instead of a != b doesn't make you clever—it makes code reviews a nightmare and your teammates question your life choices. Sure, it's bitwise magic that works for booleans and integers, but the next developer who has to maintain this code will spend 10 minutes staring at it wondering if you're doing bit manipulation or just showing off. Readability beats cleverness every single time. Save the XOR tricks for actual bit operations where they belong.

Last Day Of Unpaid Internship

Security Git Programming Backend Cloud

8 days ago 195.2K views 0 shares

Nothing says "goodbye" quite like committing the API keys to the .env file and pushing it straight to production. You spent three months fetching coffee and fixing CSS padding issues for free, and now you're leaving them a parting gift that'll have their entire AWS bill drained by crypto miners within 48 hours. The headless suit walking away is *chef's kiss* – because you're not even looking back. No two weeks notice energy here. Just pure chaos deployment and a LinkedIn status update about "gaining valuable experience." Pro tip: .env files should NEVER be committed to version control. They contain sensitive credentials and should always be in your .gitignore. But hey, when you've been working for "exposure" and "learning opportunities," sometimes people learn the hard way.

Make No Mistakes

AI Security Programming Backend

8 days ago 224.0K views 0 shares

Someone just asked an AI to "vibe code" their entire application and now they're shocked—SHOCKED—that maybe, just maybe, they should've thought about security before deploying to production. It's like building a house by vibing with a hammer and then asking "hey, should I have used nails?" The beautiful irony here is that they're asking for a prompt to fix security issues in code that was generated by... prompts. It's prompts all the way down. Next they'll be asking for a prompt to write prompts that generate prompts for securing their vibe-coded masterpiece. Pro tip: If your development methodology can be described with words like "vibe," maybe don't skip the part where you actually understand what your code does before yeeting it into production.

Vibecoding Side Effects

Security Webdev Programming Databases Backend

9 days ago 221.5K views 2 shares

You know you've entered the danger zone when you're vibing so hard that you accidentally store passwords in plaintext AND make them globally unique across all users. The error message is basically tattling on poor [email protected], exposing their password to everyone who tries to register. This is what happens when you skip the "hash your passwords" lecture and go straight to "let's just see if it works." Somewhere, a security engineer just felt a disturbance in the force. This registration form is basically a GDPR violation speedrun. Not only are passwords stored in a way that allows collision detection, but they're also casually revealing other users' email addresses in error messages. It's like a two-for-one special on security nightmares.

Weird Way Of Making Things Work

Windows Programming Linux Debugging Backend

15 days ago 244.9K views 0 shares

Oh, the absolute AUDACITY of this code! Someone out here literally checking if they're running on Windows and then just... *casually lying to the entire application* by setting a fake environment variable claiming it's Linux. It's like showing up to a costume party as yourself but telling everyone you're someone else. The sheer chaos energy of "my code only works on Linux but I'm stuck on Windows, so I'll just... gaslight my own program into thinking it's Linux" is truly unmatched. Does it work? Maybe. Should it work? Absolutely not. Will it cause mysterious bugs six months from now that make future developers question their career choices? Oh, you BET it will. This is the programming equivalent of duct tape and prayers, and honestly? Sometimes that's exactly what ships products.

Any One Using This Key

Security Networking Devops Linux

17 days ago 241.0K views 0 shares

Someone actually hand-wrote their OpenSSH private key on paper. Let that sink in. The same key that's supposed to be kept secret, never shared, and definitely never exposed to human eyes for more than a millisecond is now immortalized on graph paper like it's a high school math assignment. This is either the most paranoid backup strategy ever conceived (EMP-proof! Ransomware-proof! Works during the apocalypse!) or someone fundamentally misunderstood the "write it down somewhere safe" advice. Either way, I'm impressed by the dedication to transcribing hundreds of random characters by hand. The real question is: did they actually verify it character by character, or is this just an elaborate piece of security theater? Pro tip: If you ever need to restore from this backup, good luck distinguishing between that lowercase 'l', uppercase 'I', and the number '1'. Your SSH connection will be rejecting you faster than a senior dev rejecting a PR with no tests.

I Dislike Large Variables, I Don't Like Vertically Long Functions, And Hate Comments Because They Distract Me. I've Started To Change Though After Having To Go Back To Things Like This.

Programming Python Debugging

19 days ago 246.0K views 0 shares

I Dislike Large Variables, I Don't Like Vertically Long Functions, And Hate Comments Because They Distract Me. I've Started To Change Though After Having To Go Back To Things Like This.

Nothing quite like reverse-engineering your own code and realizing you've basically written an encryption algorithm for yourself. Single-letter variables, nested ternaries, bitwise operations thrown in for flavor, and logic so compressed it could be a ZIP file. That function is doing approximately seventeen things at once while looking like someone sneezed on a keyboard. Good luck figuring out what r , t , c , and p represent without a Rosetta Stone. Turns out "clever" code is just future you's problem. And future you is standing there like a confused mob boss trying to decode what past you was thinking. Spoiler: past you wasn't thinking about readability. Pro tip: if your function needs a PhD to understand, maybe add a comment or two. Your future self will thank you instead of plotting revenge.

Browse