Pun of the day

Boss: I heard your colleagues hate dealing with code you wrote. Why?
Me: No comment

Code comments be like....

"I wrote the code, I have to maintain the code, I wont need any comments"

*some months later*

I found the greatest stackoverflow comment:

Debugging comments be like...

Comment your own code.

"But nobody except me will see..."

COMMENT YOUR OWN CODE!!!

commentingSkills++;

The way to resolve the issues

Oh, man, I just realized I haven't ranted one of my best stories on here!

So, here goes!

A few years back the company I work for was contacted by an older client regarding a new project.

The guy was now pitching to build the website for the Parliament of another country (not gonna name it, NDAs and stuff), and was planning on outsourcing the development, as he had no team and he was only aiming on taking care of the client service/project management side of the project.

Out of principle (and also to preserve our mental integrity), we have purposely avoided working with government bodies of any kind, in any country, but he was a friend of our CEO and pleaded until we singed on board.

Now, the project itself was way bigger than we expected, as the wanted more of an internal CRM, centralized document archive, event management, internal planning, multiple interfaced, role based access restricted monster of an administration interface, complete with regular user website, also packed with all kind of features, dashboards and so on.

Long story short, a lot bigger than what we were expecting based on the initial brief.

The development period was hell. New features were coming in on a weekly basis. Already implemented functionality was constantly being changed or redefined. No requests we ever made about clarifications and/or materials or information were ever answered on time.

They also somehow bullied the guy that brought us the project into also including the data migration from the old website into the new one we were building and we somehow ended up having to extract meaningful, formatted, sanitized content parsing static HTML files and connecting them to download-able files (almost every page in the old website had files available to download) we needed to also include in a sane way.

Now, don't think the files were simple URL paths we can trace to a folder/file path, oh no!!! The links were some form of hash combination that had to be exploded and tested against some king of database relationship tables that only had hashed indexes relating to other tables, that also only had hashed indexes relating to some other tables that kept a database of the website pages HTML file naming. So what we had to do is identify the files based on a combination of hashed indexes and re-hashed HTML file names that in the end would give us a filename for a real file that we had to then search for inside a list of over 20 folders not related to one another.

So we did this. Created a script that processed the hell out of over 10000 HTML files, database entries and files and re-indexed and re-named all this shit into a meaningful database of sane data and well organized files.

So, with this we were nearing the finish line for the project, which by now exceeded the estimated time by over to times.

We test everything, retest it all again for good measure, pack everything up for deployment, simulate on a staging environment, give the final client access to the staging version, get them to accept that all requirements are met, finish writing the documentation for the codebase, write detailed deployment procedure, include some automation and testing tools also for good measure, recommend production setup, hardware specs, software versions, server side optimization like caching, load balancing and all that we could think would ever be useful, all with more documentation and instructions.

As the project was built on PHP/MySQL (as requested), we recommended a Linux environment for production. Oh, I forgot to tell you that over the development period they kept asking us to also include steps for Windows procedures along with our regular documentation. Was a bit strange, but we added it in there just so we can finish and close the damn project.

So, we send them all the above and go get drunk as fuck in celebration of getting rid of them once and for all...

Next day: hung over, I get to the office, open my laptop and see on new email. I only had the one new mail, so I open it to see what it's about.

Lo and behold! The fuckers over in the other country that called themselves "IT guys", and were the ones making all the changes and additions to our requirements, were not capable enough to follow step by step instructions in order to deploy the project on their servers!!!

[Continues in the comments]

College was a hell lot of fun.

Every. Single. Time.

Protip: always check for snarky comments before pushing

Hope I'm not late with this one.

Lol 😜😜😂😂

Some comments are helpful, some aren't

Shout out to devs who put comments in your code I'm so done with my team rn

Also we have slack for a reason stop texting me to update everyone on changes...

Comments it out and flies away..

Couple years ago, I wrote a game in assembly.
Yesterday, I tried to look at the source, and realised there isn't a single fucking comment.

Write comments.

You know what really grinds my gears?

Seeing a 5-line comment, that have absolute no value, for a variable declaration.

Example:

/*
*
* String that holds a delivery address.
*
*/
public String deliveryAddress;

Always.

After opening the legacy code and finding out that the entire shit has 15000+ LOC and without proper comments

Told ya!

True story

When you properly comment your code.

I sometimes write code by first putting comments and then writing the code.
Example
#fetch data
#apply optimization
#send data back to server
Then i put the code in-between the comments so that i can understand the flow.
Anyone else has this habit?

Code never lies..

//Salt

Where do I buy this?

Stack overflow is really gold sometimes!

Writes program.
Doesn't comment code.
*Yeah totally gonna remember everything* 🕶

*5 weeks later*
what the heck was I writing.? 🙄😥😭

Why I love devRant so much?

Unlike other communities we are not abusing picture comments :)

When you check the comments under GitHub and most of them are +1

Was just browsing through some old screenshots when suddenly...

No wonder my installer doesn't work...

No comments😐😐

Lol true

Commenting for future reference

Code never lies... Comments sometimes do... 💻💻

Ouch, I got pwnd by the google chromium developers :D

Shouldn't be necessary if you just write understandable code xD..... Some people just write stories in between 2 lines of code....

While looking up some code on github:

This is true.

Anybody else here has a coworker who insists on having comments everywhere and writes code like this?

// Get foo
foo = getFoo();

// Check if foo is greater than bar
if (foo > bar)

Or is it just me?

Unpopular opinion: I like documenting my code. I think it has a somewhat calming effect

Be me, and write a reminder down with a // in front of it.
On a piece of paper.

I hate myself. Really.
Last week I wrote a function to handle file uploads and at some point I left this very useful comment.
Do I know what to fix? Absolutely fucking nope.
I want to punch me from last week in the face

I promise (for myself) I'll comment my code from now on...

Today I created my first public repo... I've never commented my code so much.

No need of comments!

So I saw a guy looking frustrated today, staring at a big wall of code that he needs to debug.
A 3000 lines file, of only 2 methods, with variables named using single characters, and 0 comments except for 1 right in the middle of the file.

//now we average

I usually offer help, but this is something I had to run away from :(

How can testing and debugging 10000 lines of uncommented, obfuscated code get worse?

Testing and debugging 10000 lines of uncommented, obfuscated code in visual studio.

Always comment your code.

Can't deny ;)

The proper use of comments is to compensate for our failure to express ourself in code.

Quote of the book "Clean Code" by "Uncle Bob".

#ShotsFired

Missed out on 100% on a uni assignment because of not enough comments. The undocumented function in question was a one-liner called 'checkValidLength'

'checkValidLength'? Uh... I don't know what that does, let's take a look inside...

'return len(thing) == 4'? Nah... Needs a documentation comment. It's just too obscure.

Are you fucking kidding me? It would take longer to read the comment than the function!

Here, this is a rasp. It's used for filing things. With it, you'll find some nice documentation telling you precisely how far up your arse you can shove it.

When you look around a site, find a comment page and it looks like that.

- "Where is the form? Oh... Wait... Those misplaced 1px lines look weird.... *tap* Holy shit! There it is!"
- What data should I put in which field again?

"Well. I don't want to figure that out. Time to go ba... Where is the navigation? 😲"

Another stack overflow rant.

I had a disagreement with a self proclaimed "high repper" last night. We exchanged words in the comments of one of my questions.

Later (about ten mins) i see that another one of my questions has been closed and marked as duplicate - by this same fuck-knuckle. He has obviously gone to my profile and then gone out of his way to harass / bully me by doing this.

The 2 questions are absolutely not duplicates and he has marked them as identical.

I go to his profile and his headline thing is

"Low reppers hate closers but they need to go bitch about it elsewhere"

If anyone on here doesn't understand why SO gets a bad rap, it's specifically due to complete cunts like this guy.

If you happen to be on here and recognise yourself from the really cringy "low reppers" comment on your profile, then all I have to say to you is that you are a complete an utter ballbag; a tool; an arsehole of the highest order.

Fuck you and all your spawn.

!rant

Someone just downvoted four of my answers on Stackoverflow just because I commented on one of his answers that "please include some description, just code won't be helpful"

PEOPLE IF YOU CAN'T ACCEPT YOU ARE WRONG THEN GET THE FUCK OUT FROM OUR COMMUNITY AND STOP RUINING IT.

The comment on the source code of hasthelargehardroncolliderdestroyedtheworldyet.com is the best one I've seen so far :D

print ("Hello World") # prints hello world

"A common fallacy is to assume authors of incomprehensible code will be able to express themselves clearly in comments" -Kevlin Henney

Shared by codechef on their Facebook page. Not sure who the original author.

But it sure does make a pretty good header for your code. ;)

#DontMessWithMyCode

A brave soul.

This had to be shared

Comments.

Code never lies. Comments sometime do.

This is how most comments in code are. Why are you telling me it's a coffee cup, I can fucking see it's a coffee cup, who owns it and why is it right here? Are you putting coffee in it or something else?

If you're gonna comment a lot or a little, at least be consistent. I just read some code like this:

//prints "are you ready?"
printf("are you ready?");

//get the value
int findVal(int x) {
/* some fucking complex algorithm with no comments whatsoever that seems to have an error messing everything up */
}

Our PM found a contractor, results as expected..

Contractor: "The file you supplied is corrupt, some areas are greyed out and damaged"
Me: "😐, do you mean the comments?"
Contractor: "I'm not sure what you mean 'the comments'"
Me: "Does the file work as expected?"
Contractor: "Yes"
Me: "Strange! I'll have a chat with our PM and get this issue resolved right away 😉"

...

if(!contractor) {
return Promise.resolve()
}

@dfox
Feature request for favouriting a comment.

Some comments are really helpful/awesome.

I just finish "rebuilding" a page that I have built last year. My Js file (jQuery) went from 1200+ lines to 600..

I rewrite everything, the functionality is the same but the code is mush more cleaner.
Soo bad and redundant code.

Although comments where very helpful.

Feels good.

Someone just asked me to properly indent my code and add comments.
feeling molested.

my own program is confusing me :)

it'll be fun waking up tomorrow trying to solve a hard problem…

oh shit i forgot to add comments🙃

Sometimes I go ridiculously hardball on my comments in order to gain a better understanding of what I'm trying to accomplish

I worked with this guy at a startup one time, and just to annoy me, he would write commit comments describing how I was such a bad developer, or how I was such a horrible person. After like the 15th time he did this, I decided to be totally unprofessional and do the same for him... our commit comments quickly turned into a conversation where we would just insult each other (as a joke).

The original developers of the startup no longer work there (including me and him)... I wonder who's reading those comments now.

Hi guys,
I did disappear à long time, you know personal problems...
But I'm back to work now, and I was watching cppcon, when...

Why would you submit a pull request with the addition of such a comment and expect me to approve? What the hell is wrong with you?

When I was in school, my books would always have poems or song lyrics written on the corners of pages or empty sections.

I'm still thinking if o should carry the habit on and do the same in the comments:

/*
* Does anybody here remember Vera Lynn?
* Remember how she said that
* We would meet again
* Some sunny day?
* Vera, Vera
* What has become of you
* Does anybody else in here
* Feel the way I do?
*/

When my coworker doesn't want to believe his code is inconsistent, yet he changes the syntax for commenting 3 times over 10 lines.

Writing comments done right by udacity

/**
* We couldn't come up with a good name for this class. Then, we realized
* that this lesson is about RecyclerView.
*
* RecyclerView... Recycling... Saving the planet? Being green? Anyone?
* #crickets
*
* Avoid unnecessary garbage collection by using RecyclerView and ViewHolders.
*
* If you don't like our puns, we named this Adapter GreenAdapter because its
* contents are green.
*/

When I return to development of my code that wasn’t commented

After reading those comments, everything starts making sense

Add no comments or documentations whatsoever during my initial years of coding (when actually I used to write code worse than a constipated elephant's shit).. In my mind I would be like "This is quite clear-cut.. A first grader will be able to understand this code.."

But then I had to debug my own code barely some 1-2 months later and I figured out the importance of good comments and documentation..

I am sure this has happened to all of us in some extent with some variations.

Colleague not writing comments on code.
Ask him something like "How am I suppose understand that piece of garbage you have written when there is no comments or documentation?"
This keeps happening for a long time. Some time after, I write a kernel module using idiomatic C and ASM blocks for optimizations (for some RTOS) and purposely not write neither documentation nor comments.
When he asked for an explanation, I answered to everything he questioned as general as I could for "that trivial piece of code".
After that he always documents his code!
Win! 🏆

Keeping old and unused code blocks commented out and not deleting them immediately is the equivalent of leaving that bottle of soy sauce in the fridge even though you know very well that you won't use them ever again.

Comments should describe the why and not the what and always be up to date ... or this will be the result.

Choose one language that will stay and be used universally by every coder, and the others will vanish

I choose Python, what about you?

Inner Peace!

THE ULTIMATE BERMUDA TRIANGLE OF A CODER

Fuck the way comments work in xml. I want to write a 2 word comment but before that I apparently have to make an ascii art mona lisa. Infront of and after the comment.

Some guy in Medium said this....

Then fire all python devs.

Oddly satisfying devRant +1s

¯\_(ツ)_/¯

The one who said "Code should comment itself" must not have used assembly.

I literally wrote this 30 seconds ago and I can't work out what it does now...

literally lol'd out loud when I saw this. Found in the source of popular event loop library libev, in ev.c line 214:

When you're severely tired of your life

$str = str_replace(array("\{","\}")," ",$str);

//Replaces with spaces the braces in cases where braces in places cause stasis

getting rid of legacy code - and a great comment :D

Looking thru some old code, i lol'd

Who the fuck writes 2k lines of code without a single fucking comment!?

Inherited project from another company that the owner wants updated rather than rebuilt.

The comments could write a programmers joke book as you can tell it's been passed between multiple developers.

This is a literal excerpt
//Not sure why this line needs to be here but it breaks without it
//Nope I don't know either
//FFS now I have to deal with this. Thanks guys :/

After realizing how life-saving commenting is..

When you get to work Monday morning and realise just how little fucks you gave on Friday.

when you find a comment you wrote to yourself like three months ago after you already "fixed" the problem...

############
# REMINDER
# below has been modified to save half masked images
# you did this quickly to make a movie for a talk in late 2016
# don't forget to change it back to save fully masked images
# which are the ones that are actually used in processing
# END of pitiful attempt to save yourself from future aggrivation
############

at least I anticipated that this would happen...

Very effective

That moment when the first comment in your first SO answer is:

"This should be a comment"

There are still old youtube comments from my younger self to be found on youtube. Delete every evidence!

that moment when one of your comments have more ++'s than most of your rants! 😂

Don't you hate it when you come across a old internet argument but one of the people deleted all of their posts so now you just see a bunch of out of context replies.

Me: Can you do the javadocs comments
Coworker: I've never done that, *looks for it on google*, I can't do it, I don't know how.
Me: Did no one asked you to comment you code at school?
Coworker: Yeah, but only the ones with '//'
Me: Ok, bring me coffee

From r/unixporn:

Please remember that comments in html do not start with //. This comes from the website of one of the most important gas and electricity distributor in Italy btw...

Friend - could you comment your code, so I can review it pls.

Me - *comments "gets shit done" ,
"Does some shit ",
"I really don't like commenting my code "

Commented all of my code. More than 1000 lines, teacher didn't read it....

Is it normal for every stupid, arrogant, selfish person to talk all kinds of bad stuff about my app and attack me personally on the play store? It's just a soundboard and it's free you pricks, be grateful for once and don't mind the god damn ads so much. I can't believe that shit.

A comment line can save the sanity of many programmers

Wanted to search something in my old code. Understood why people use comments.. :/

I have a coworker who comments every line of code he writes and it doesn't matter how simple the code is and it drives me crazy when I have to look at it. A real life example:

// Gets the total length of the server name string
var total = serverName.length;

“Good comments explain why, not what,” says Andy Marks. “Do more of the former and none of the latter. A well named method or variable will beat a well-written comment every day.”

More random code from github

I don't know why I was reading it, but I loved it :P

When you add comments and your code isn't working so you just leave it alone for 2 hours and when you come back it works

Achievement of the day: I managed to use "begotten" in a comment :)

Fuck man. I keep forgetting to comment my code for the sake of my future self.

Your favourite comment?

My team was working on a legacy system, one part of it is an assistant, sadly required as global variables.

Being a non-english-first-language company, some dev years ago thought shortening said assistant to "ass" would be a wise idea - less to type, right?

When we redid the application 2016 part-by-part, our code needed to define 3-4 global variables starting with the "ass" prefix for the legacy parts to work. The colleague who was tasked with this is a fine gentleman from England.

Later as I read through the commit, I found 5 lines of code following 20 lines of comments explaining and deeply apologizing for "ass", "ass_open", etc.

The same dev also had a "HACK OF THE YEAR" comment he moved around when time constraints made a less-than-optimal fix necessary which was worse than the last "highscore".

Haven't coded for a few days, returned to my github project to find one of my co-workers has gone through every single line in all of the scripts and added passive-agrresivd, sarcastic, comments about what they do.

Thanks.... I guess....

6 lines of comments.
7 lines of code.

Gr8...

I found this in the "cinnamon.css" of my current theme lmao

Why should devrant have comment chaining feature?

Example attached.

Source: Imgur

Boss: Why have you commented out these lines of code?

Me: I don't have the heart to KILL them..

To whomever worked on this system before I joined, thanks for spending time peppering the codebase with quotes from "The Emperor's New Groove," it certainly makes debugging this broken radio driver more interesting. But... It would've been nice if you spent that time writing real tests. We're a few weeks from handing this off for environmental testing before launch (real, physical launch - it's a satellite), and the radio suddenly won't respond, and we've got no idea where to start looking.

/*Why this website does not use slashes to the front of all the comments on a rant is beyond me!*/

Sometimes I write so many comments that it's hard for me to read the code :/

I'm curious: which do you like better? Atom or VS Code?

"There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-one errors."

Really wish the world was less volatile when it comes to opinions!

Commented on a video about fallout 3 being an important game and a tonne of people were bitching and insulting the creator because they think New Vegas is better...

I commented saying I prefer fallout 3 and instantly got bombarded with insults... Ugh

Hope none of my games will ever cause this shit -,-

Meanwhile in C++ world....
My friend wrote a class and he wrote main to demo how to use it.
He is the nicest programmer I've ever seen...😀

I Remember what my senior told me once:

"You know you're in the wrong job when you see source code filled with comments written by ur senior dev scolding other devs for code fuckups"

Back then when I was working on a website logic, I didn't want to comment my code. Despite that, I wrote some things which were obvious and I thought it would be funny to explain obvious things in code. I made a joke out of commenting.
Recently I needed to use a part of the code for a different project and the comments were exceptionally helpful and I would be lost without it.

So, kids, comment your code!

I let my programming buddy comment all the code I write. He's great. His comments looks like this:
/*
I am groot!
*/

The student assistant gave me a half point penalty for writing down to much comments! Direct translation:
To much of this kind of comments is not needed, the code itself is clear on its own.

Code never lies but comments do !

Should I be concerned?

Everything is clear now

If you comment your code like this, I'd like you to rethink your life choices.

This is a project we need to work on in university. The code was given to us.

I just started commenting my code. I know, its horrible i havent done this earlier..
I actually enjoy it now, i can express rage, write small jokes for myself to read next time i gotta edit the code, or just remind myself how fucking stupid i used to be

Code comments #1: A way to document bad code that wasn't reduced to it's essentials and thus unreadable. Bad.

Code comments #2: A way to explain for non-programmers how the code works. Wrong place.

Code comments #3: Company policy. No one really knows why, but others do that, so we better do it to. The management sucks.

Code comments #4: Because some hip methodology/guru describes how to document code. After a few years, when the methodology has been (unofficially) forgotten, everyone still comments the code the same way. The old management sucked.

Code comments 5#: For insecure programmers who want to convince them self they understand the code they've written. Maybe apply at McDo?

Code comments #6: Some programmers are apparently paid by lines of code. Possibly understandable.

// Comments, anyone?

When you find a 'TODO' comment deep in a crucial function, that you know have been there for at least 5 years. :S

Just read this comment in my code from a few months ago... I guess I was in a strange mood at that time..

// Listen for fuckers. Also known by their muggle name: users.

Has to review another Devs TypeScript project. And what do I find?

A single ts file with 700 lines of uncommented pure hard logic

HOW. IN THE WORLD. COULD IT BE SO DIFFICULT TO COMMENT THE CODE I WRITE MYSELF ?

After my first project (you know, the "Working project I made for fun long ago" code everyone did once, but when you look at it again it looks like sorcery and there's no way to understand it ?), I decided that I'd comment almost everything I'd do... But...

When I begin a project, it's fiiiine and I do my comments the way they should be... AND THEN, WHEN DIFFICULTIES ARRIVES AND I START TO BE TIRED (ie : always) THEY START TO INCLUDE INSULTS OR WEIRD JOKES ABOUT THE PROGRAMMING LANGUAGE, MOVIES REFERENCES, AND SOMETIMES THEIR LANGUAGE VARIES. (Like, that project you're doing in English and suddenly there's a comment written in French in the middle of that)

Soo, yeah, even if I do comment my shit now, it isn't more helpful, lol. Maybe I should listen to relaxing music when I code err.

Oh, comments. Damn comments. Someday I'll do those correctly. Maybe.

Let's try this.

In the project I'm working there is an strict rule : NO COMMENTS!!!

I mean wth, the times I've spend hours trying to understand the crappy legacy code in VB.Net that has been there almost decades, that wouldn't happen with comments, I know i know there are some supernatural developers that think in binary and their eyes work as compilers, but I'm not like that, so seriously go to hell.

P.S. Of course I follow that rule, after all, my code is so damn perfect that even a baby can understand it.

jk

My internship company does not believe in the concept of 'commenting'. They just tell me: "Ahh just write readable code!
Yeah that's cool until I need to read out thousands of lines of javascript without a single comment!

And I go like I can swear I've never seen this before

Honest, they are. 😆

#define TRUE FALSE
//Happy debugging suckers

You know you are fucked, when you find a comment asking "What's happening here?".

Maintaining old code as comments, coz... you never know when that bug in your commented code turns out to be the next big feature.

/*
People on here keep using single-line comment for multi-line comments. (Sighs deeply)
*/

Code never lies,

Comments sometimes do... 🤔

What's the funniest comment you've ever come across in someone else's code? 🙃

Write comments like Morgan Freeman describes how the software was build.

When you accidentally commit and push code that has massively commented out sections that you meant to remove >:/

While I was still in University I didn't valued much the importance of comments and documentation, mostly because my projects were small and I was working on them​ by myself. Frankly, writing comments felt like a waste of time those days.

Now that I'm a junior developer working with an existing code base and together with other devs I couldn't be more grateful seeing those green lines of human readable strings. Without them I would have struggled more and probably been less productive.

*Writes something I think is clever
*Write like a 3 sentence comment explaining why it's clever.
*Smugly run.
*Doesn't work.
*Quietly erase line and comment.
*Repeat

Let's do a poll.
➕➕ only if your language of choice is:

I just took over a new project from a brand new client today. It's an Android app that he said needed some updates and refactoring, and he said it wasn't well documented but he would add some comments for me before giving me the code. He gave me access to the code today and one class in it is over 1200 lines long with exactly 4 methods in it... the shortest method is still over 200 lines long. There is one comment at the very top:
// Needs refactored.

... gee thanks.

A client's company will be sold, including the code we've had written for them. But it was the usual we-got-no-time project, so we cut the documentation.
Well, guess who has seven days left to add comments on a ~15k custom-PHP-lines project (RESTful Backend)
After that, some other Dev _might_ be able to understand at least something.
Also, I'm doing huge refactoring, improvements of code-smell and restructuring the whole project.
Maybe, our company stays as a development company for the new client but maybe not. So I'm paying now for being "lazy" two years ago.

Last 4 days, struggling to get ship it from a Dev who is reviewing my code.

The comments have already piled up more than the LOC submitted.

The code review consists of just 2 interfaces and a pojo. Hardly 20 LOC in total, excluding javadocs.

I hope it gets ship it soon.
Wish me luck.

Stackoverflow #1
Me posting question about how to prevent error.
User1: You answered your question. Its because of the error.
Me: I know. And want it gone.
User1: Proposes working yet somehow horrible workaround.
Me: Yes, that works, already did that. But i want to know why it happens.
User: Your question says you want a solution and it is one.
Me: One that doesn't solve the problem.
User2: Just give up. Don't try to find a better one.

Stackoverflow 2:
UserQ: Question how to...?
Me: Use this and that.
UserR: That is not an answer, so i downvoted and requested review.

I don't know a second community that is anti-encouraging like SO.

Is it odd that I prefer to not put a space before single-line comments? For example, I prefer
magic(); //Does magic
over
magic(); // Does magic

!Rant

when you join a comment conversation... i know it's not an original post, but i love these!

Apparently someone decided to use comments on the tracklist of this album.

No comments...

When orator becomes a programmer.

Ah yeah

That moment during your internship when you work on a project using a framework you're not familiar with, with no doc, and absolutely no comments, and you find a file with 1.3k lines of code without the ability to contact the previous dev

Code never lies.
Comments sometimes do.

!rant

Having lots shitty comments and lots of shitty rants is like having passive income, the ++ come slowly but surely.

Hold on . . :D

What's your best code comments ?

Here is mine ! Wrote few days back..

I rarely comment my code.

But when I do... I do it in production.

Awful idea of the day - Have a programming language with no comments, but regex preprocessor macros. Use macros to define your own comment syntax and strip them before compiling.

#define /\/\/.*//

Dear last dev, thanks 4 leaving little 2 no //comments as u possibly could. 😑😣😢😠

Please //comment ur code!!