Menu
My code doesn't work, I have no idea why. My code works, I have no idea why.
Home
Hot
Random
Search
Browse
AI
AWS
Agile
Algorithms
Android
Apple
Backend
Bash
C++
Cloud
Csharp
All Categories
HTTP 418: I'm a teapot
The server identifies as a teapot now and is on a tea break, brb
HTTP 418: I'm a teapot
The server identifies as a teapot now and is on a tea break, brb
Obvious comments Memes
Posts tagged with Obvious comments
How People Write Comments In Code
Programming
Debugging
9 months ago
239.4K views
0 shares
Nothing captures the absurdity of code comments like this pizza box stating the blindingly obvious. After 15 years of reviewing PRs, I've seen it all—from stating "this increments i" on i++ to documenting that water is wet. Meanwhile, that cryptic 200-line algorithm that actually needs explanation? Zero comments. The real dark magic happens when you revisit your own code six months later and wonder what drugs you were on when writing it. Future you will thank present you for meaningful comments—not for pointing out that a box contains pizza.
But It Is Impossible To Understand Code Without Such Comments
Programming
Debugging
10 months ago
193.8K views
1 shares
The pinnacle of useless documentation right here. Just like when your colleague writes // increment i by 1 next to i++ but completely fails to explain why that Byzantine sorting algorithm exists in the first place. The real tragedy is when you return to your own code six months later and find comments like "Fix this later" with no explanation of what "this" is or why it needs fixing. Meanwhile, the actual complex logic remains a mysterious black hole with zero documentation. Pro tip: If your comments could be replaced by a fortune cookie message and provide the same level of insight, you're doing it wrong.
Code Comments Be Like:
Programming
Debugging
Testing
10 months ago
226.5K views
0 shares
Ah yes, the classic "stating the obvious" comment. The car door literally says "This DOOR is Blue" while being clearly silver/white. It's the programming equivalent of writing int x = 5; // this is 5 instead of explaining why x needs to be 5. After 15 years in the industry, I've learned that future you will hate past you for these comments. The real documentation we need is "WHY this door is painted differently" not "WHAT color it obviously isn't." Just like your code should explain the how, your comments should explain the why.
Captain Obvious: The Code Commenter
Programming
Debugging
10 months ago
237.1K 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! 🙄
How I Comment My Code
Programming
Debugging
Testing
1 year ago
162.9K views
0 shares
The pinnacle of software documentation right here. We spend eight years getting CS degrees just to write groundbreaking comments like "Open box before eating pizza" on our code. Nothing says "senior developer" quite like stating the painfully obvious while leaving the actual complex logic completely unexplained. The best part? Six months later, even YOU won't remember what that cryptic algorithm does, but at least you'll know when to open the pizza box. Pure documentation brilliance.
Code Comments Be Like
Programming
Debugging
Testing
1 year ago
208.9K views
0 shares
OH. MY. GOD. The absolute state of code documentation! 😂 A stop sign with a sign underneath saying "THIS IS A STOP SIGN" is the PERFECT metaphor for how we comment our code! Like, honey, I can SEE it's a for-loop, you don't need to add "// this is a for-loop" underneath it! The sheer AUDACITY of developers explaining the blindingly obvious while leaving the actual cryptic nightmare code completely undocumented. Meanwhile, that function that summons demons when Mercury is in retrograde? Zero comments. ZERO! But don't worry, that variable named 'x'? Thoroughly explained as "x variable." THANK YOU, CAPTAIN OBVIOUS! 💅
LG 32U990A-S 32-Inch Ultrafine 6K (6144 x 3456) Nano IPS Black Thunderbolt 5 Professional Monitor, 60Hz, DisplayHDR 600, Speakers, HDMI 2.1, DisplayPort 2.1, USB-C, Tilt/Height/Pivot Stand, Silver
Affiliate
Monitors
LG
The World’s First 6K Monitor with Thunderbolt 5 - Crafted for creatives who demand more, the LG UltraFine evo brings 6K clarity, stunning clarity, and rich color to every frame. With Thunderbolt 5 an…
Code Comments Be Like
Programming
Gamedev
Unity
Debugging
1 year ago
266.0K views
0 shares
Ah, the magnificent art of code documentation! This meme perfectly encapsulates what happens when developers "comment" their code. Instead of writing something useful like "This function handles user authentication with proper error checking," they just label obvious objects with stunning insights like "Trashbin." It's the programming equivalent of putting a sticky note on your refrigerator that says "Cold Food Box." Thanks, Captain Obvious! Next you'll be commenting your variable declarations with "// this is a variable" and loops with "// this repeats stuff." The true irony? Six months later, you'll still have no idea why you wrote that algorithm the way you did, but at least you know where the digital garbage goes!
Today's picks
Beelink Mini PC, AMD Ryzen 7 6800U (8C/16T, up to 4.7GHz), 24GB LPDDR5 500GB PCIe4.0 SSD, SER5 MAX Mini Desktop Computer Support 4K@60Hz Triple Display/DP1.4/HDMI/Type-C/WiFi 6/BT5.2 for Office/Home
Affiliate
$459.00
Great Question Yes Looks Like You're Cooked
Cloud
490.7K views
18 days ago
Startups be like.
Programming
76.1K views
2 years ago