Pun of the day

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

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

*some months later*

Code comments be like....

Hope I'm not late with this one.

> Comments are there only for you, please delete them before pushing your code.

I want to kill everyone who suggests that, slaughter them like animals!

Going through the previous guy's code. Dude got his comments on point.

Said my code is self explanatory and doesn't need comments.

After few minutes "wtf is this shit?".

Had a PR blocked yesterday. Oh god, have I introduced a memory leak? Have I not added unit tests? Is there a bug? What horrible thing have I unknowingly done?

... added comments to some code.

Yep apparently “our code needs to be readable without comments, please remove them”.

Time to move on, no signs of intelligent life here.

By playing with Facebook source code in browser, you can enable GIF and Markdown, Tip Jar & many more options in comments.

One of the coolest good bye message I have ever seen in my company...

The code is so clean with proper comments...

"Don't waste your time on writing comments or documentation, as long as the code works!" - My (Ex-) Coworker

When someone asks you to add more comments to your clean code.

Love finding weird comments like this in 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 doesn't lie, comments do.

True story

Code never lies, comments sometimes do

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

If God left comments in his code...

Where do I buy this?

good code > bad code + good comments 🤔

When I decided to comment my code

What kind of psychopath comments code UNDERNEATH??

What if we developerized our proverbs?

1. A bad developer blames his tools.

2. Code speaks louder than comments.

3. Birds of a text editor flock together.

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

Do you have any funny comments in code?

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

I befriended a much-older dev who's notoriously known for cursing in source code comments.

His best comment was F.I.S.H., which is his cursing acronym for "fucking incredible shitty hack"

Seen at work in code:

<!-- DO NOT REMOVE CONTENTS PLACED HERE //TODO: Would have loved if some one also had said why we should not remove this -->

Lol

This week I've been struggling with dense, overly-complex code written long ago by someone who didn't add a lot of comments.

Hello again, past me.

My coworker comments every line of code I think the code is not readable!

Stop bitching about having to write comments, they are important whether you like it or not. Trust me nobodys code is "that good" 😒

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

Code never lies, comments sometimes do.

I just changed a bunch of comments, log entries, and removed some blank lines from one of my controllers. Zero functional code changes. Everything worked before; now it runs only half the code, breaks, and throws strange errors.

Fucking hell.
Screw today.

Other Dev left just as we hit beta and refactored all his code without documentation... Not even fucking comments...

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

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

Anyone coding like in the right picture? 😮
(I mean the comments with smileys not the code part)

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

Leaving TODO comments in code

Comment the "why", not the "what". If your code needs comments to explain what it does, rewrite the code (use good, descriptive identifiers).

piece of code: *not working*
me: okay, i can try this again later
me: *comments it out*

4 hours later

me: omfg why are there so many comments??? :(

Code never lies. Comments sometime do.

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

Find a great project on github=> want to find out how it works => open the source code =>zero line of comments

I'll include this in all my projects from now on 🕷️

You want comments in my code. ;)

Putting todo comments in code knowing it'll never get done.

Bit of a guilty pleasure.

"When code and comments disagree, both are probably wrong."

- Norm Schryer

Code never lies, comments sometimes do.

Me begging myself to add comments to my code.

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! 🏆

Me : Today we have to demonstrate our progress to client. So remove all the dead code from the project which we had written for debugging.

** Removes all the comments

At my previous job a coworker left positive comments alongside any negative ones on my code. “Nice job here. Very clean”, or “nice use of X design pattern here!” Kinda made me look forward to his code reviews.

Don't use code comments to list the root-admin credentials for all your servers!!!!!!

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?

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.

Going back to put in comments after you realise your code is actually going to be used by others after all

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 was deleting random comments i did in my code...
because it didnt work... then it did...

When your code reviewing the new guy and there's 50 comments for every line of code

My manager doesn’t like code comments, want us to remove from PRs 🤦🏻‍♂️🤦🏻‍♂️

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.

So my co-worker loves to tell us to comment our code, for obvious reasons.

But now I'm debugging his code, and guess what.

No comments.

Okay, maybe two comments in two different queries, but they were not that helpfull.

So now I have to debug his code, and I have no idea what I'm even supposed to look for!

Developer accused of unreadable code refuses to comment.

Reading the comments in a piece of code:
{
//Step 1 save stuff in a list
code();
//Step 3 Update the controls
morecode();
//Step 4 Resize the UI
somecode();
}

//Me thinking: where the f*ck is Step 2?

When you're asked to maintain some code that has no comments whatsoever...

Why in the flying motherfuck can't people remember the fact that other people might have to read their code?! If you're not gonna name things properly, and mess everything up with utterly useless and garbage comments (all comments are useless and garbage), then the least you can do is fucking format and indent it properly!! GAWD FAKKIN' DAMNIT!!

I cringe everytime I see improperly formatted code -_-

Me: *sees no spaces between function blocks so I format it myself*
Classmate: *Happily types code with no spaces between lines or comments and overwrites what I did*
Me: Seriously?!

Looking for the bug for 2 days. Comments out a random line of code and the bug is gone.

when the comments in code directly contradict what the code is actually doing.

Pet peeve of the day: People littering code with comments that repeat already obvious method names.

// Submits public key password
SubmitPublicKeyPassword(string psw)
{
//...
}

When the code you've taken over is filled with comments starting with:

// HACK: ...

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

:/
Project i got to work couldn't get worse
1)Legacy code
2)mathematical model based emulation
3)no proper comments
4)deadline approaching

Update log: performance improve, API rewritten, fixed all bugs reported, new features implemented, general cleanup of code, documentation and comments update
Feedback: love the new background colour!
😞

the profesor looking at my code 😂😂😂.... i have to write more comments 😅

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 "

Blessed be the person whose comments/documentation is embedded with tiny pieces of code.

Code never lies
Comments sometimes do

Nah!
Code lies too, especially when you train a neural network 😂😂

In order for the program to run smoothly, it is often necessary to add some comments to the code comments...

/***
* ░░░░░░░░░░░░░░░░░░░░░░▄░░
* ░░░░░░░░░▐█░░░░░░░░░▄▀▒▌░
* ░░░░░░░░▐▀▒█░░░░░░▄▀▒▒▒▐
* ░░░░░░░▐▄▀▒▒▀▀▀▄▄▀▒▒▒▒▒▐
* ░░░░░▄▄▀▒░▒▒▒▒▒▒▒█▒▒▄█▒▐
* ░░░▄▀▒▒▒░░░▒▒▒░░▒▒▀██▀▒▌
* ░░▐▒▒▒▄▄▒▒▒▒░░░▒▒▒▒▒▀▄▒▒
* ░░▌░░▌█▀▒▒▒▒▒▄▀█▄▒▒▒▒█▒▐
* ░▐░░░▒▒▒▒▒▒▒▒▌██▀▒▒░▒▒▀▄
* ░▌░▒▄██▄▒▒▒▒▒▒▒▒▒░░░▒▒▒▒
* ▀▒▀▐▄█▄█▌▄░▀▒▒░░░░░░▒▒▒
*/

Code reviewer keeps removing my comments saying, "This will only be read by other programmers, the code should speak for itself".

<hyperbole>
This is the exact opposite to back in uni where for every line of code they demanded 2 lines of comments!
</hyperbole>

gotta love them comments:
#TODO: move this,
#TODO: deprecated,
#TODO: fix this,
#TODO: DON'T DO THIS,
#TODO: refactor,
#TODO: CHANGE THIS

I shit you not

Going for my first code review. My colleagues and I will read through my main class, which is 832 lines long and a two-three comments.

Found in the PCIe driver code for something I have to work with:

if (false) {
// 200 lines of unnecessary code
}

You ever heard of, you know, comments?

Found my old code.

You gotta admit, that's some clean code there, considering I learned C# only for a year at that time.

But those comments....
VeRy WeLl WrItTeN, vErY dEtAiLeD, vErY gOoD

I worked about two years on a browser game without using any version control. I also thought it would be nice to have absolutely no comments in the code.

6 lines of comments.
7 lines of code.

Gr8...

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

University, Italy
We have sent our code to the professor for correction.

Professor : Who wrote the code with comments in english?

Proud student : me !

Professor : you failed to write the algorithms, and also made mistakes with a lot of English words.

I (don't) like how some people say "If your code needs comments, your code is probably ugly and should be rewritten".
Well, asshats. You have never considered complex calculations/functions or "temporary" workarounds, right?
Sometimes, you have to do it in a not-very-readable way for efficiency. There is no way around that in that case, and comments that either explain the code below or provide alternative, slower code that's commented really help others understand your code.
If I ever work with you and you don't bother commenting your code at all (or rather use slow code because more efficient code doesn't appeal to your "muh code dun need comments" approach), I will hate you.

Email chains, screenshots shared in google docs, two comments per 1k lines of code, and sticky notes are sufficient documentation, right? RIGHT?

Most Devs leave comments in their code. My boss leaves DJ Khaled quotes...

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?

Code never lies comments sometimes do

When u send ur code for review and instead of getting comments for logic u put in, u get 10+ comments regarding variable names , extra lines and formatting.
LMF

Started working on a new project.

Sent out my first code review for that repo.

An intern pinged me and blamed me that I have added so many comments to get more lines of code.

I have no words to reply him.

Picking up other developers code can be the worst sometimes..

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

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

"Remove comments" said one bright developer, when asked how to reduce code space!👍
#ohshitmoment

When in internship you have to read 150000 lines of code to make changes and the code does not have any comments, no indentation, no documentation, no wiki. You'll be like fuck this shit. I'm outta here.

Code never lies but comments do !

+++ BREAKING +++
Local developer so fucking mad he confuses code comments for Devrants

Should I be concerned?

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

Read code, exceptions, comments carefully. Double think before asking. But never hasitate to ask if you are stuck.

"Our code is self-documenting, we dont need comments" my fucking ass hole.

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"

Complex code with no comments. Like I give a fuck

Hey guys, wanna see some spaghetti code? This is some parts of Yandere Simulator. More in comments

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

Typical code life?

1. Write rough comments
2. Write more detailed comments
3. Write pseudo code
4. Write semi-working but definitely ugly code
5. Write working but very ugly code
6. Refactor the code to be nicer, check for patterns, bottlenecks and other bits and pieces
7. Push to git the "final" code
8. After few months blame whoever wrote the code
9. Refactor all the things!

---

This happened in my career more than once and still - it seems like the best option out there to get things done. What do you guys think? Should something be added/removed from this? Is this over-complicated or what?

I've learnt that you should always make descriptive comments in your code to explain it.

Code never lies,

Comments sometimes do... 🤔

when code comments be like

# loop over the array
for i in 1...10
# divide by 2
x = i / 2
# return the result
return x

That feeling of despair when you have to build a feature on top of 2 year old code with no comments

I have always believed that clean code is readable code, and if your code is readable, then it shouldn't require masses of comments to explain it. However, in the course I am being taught, we are being told that in programming, comments are massively important to help another developer understand your code and what it does. So what is the consensus of the dev community?

Do you feel comments are key, or redundant if your code is written well?

Lol!

Got 8 downvotes on stackoverflow and a bunch of comments saying I have to write code before posting a question...

Bunch of naggers out there

Is it unprofessional to put "lol" in my code comments?

These comments make me feel alive while reading code.

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.

When your Project Manager tries to find Grammar and Spelling errors in your code comments, since he couldn't find any other issues

Are you fuckin kiddin me motherfucker.. :|||

Fuckin grammarShitPMNazi

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

*Pro tip:* add comments in your code stating what you're gonna write next! This helps the reader to know what to expect!

[filename EventsTable.js]

programmers vs code comments

Going through legacy or other developers code which don't have documentation or even comments. Plus the author of the code is not working in same organisation anymore to consult. We have to understand the code like deciphering any ancient language. 😥

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.

Reviewing the code of my then new CTO, who said "I can also code and have experience in Java" - 50 lines of code, I added over 30 comments to his Pull Request. In the end, I rewrote his complete code.

Finding comments in legacy code like "too tired, fuck you" or "this implementation is dirtyyyyyy" makes me wanna punch a dev.

My company's process basically boils down to this:
-Hour long meeting to open an issue.
-5 lines of comments.
-Update three documents.
-5 days for a peer review.
-40 bitchy comments about how everything you do and love is terrible.

For a one line code change to prevent a show stopping exception.

The moment you find an ex-colleague used code comments to take someones mobile number, then accidentally committed it. It's been there over a year!

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

I don't write comments on my code

I think the best moment of writing a code is removing curses from comments and renaming variables from like "FUCKING_ITERATOR" to something more normal after everything finally works.

When someone copy and pastes code, repurposes it and leaves in the old comments that just confuse the hell out of the next dev.

This post is now dedicated for a comment debate with the topic "Is Visual Studio Code an IDE?"

I 'll see myself out. Make the comments rain

I love finding snarky comments in the code

What's your best code comments ?

Here is mine ! Wrote few days back..

I've created a code review for merging someone else's code, coz they were signed off sick for the last month.

They're making comments about how it's wrong.

It's code they wrote, but restructured to be more readable.

They wrote incorrect code that was just so illegible they didn't realise.

How do I explain this diplomatically?

Updating a legacy written by the ceo from swift 1.2 to swift 3.1
No storyboard, main controller with 2200+ lines of code and viewDidLoad method with 500+ lines of code.
Almost no comments and code is illisible.
Weeeee

I have the habit of adding //todo comments to my code whenever I need to implement something later. Very useful to just search your code for "todo" and see what is left to do.

That is all very well, but I just searched my project for "todo" and there are SO MANY //todo comments in the third party dependencies...

You know you need to stop debugging and sleep when you start rearranging your comments in the hope that your code will work!

I hate ppl who don't indent code and those who don't add proper comments to explain three crap that they've created

Every developer thought what the hell my colleague is writing in code.

After watching own code after a year, who the hell is the developer.

Oops it me. No comments :)

Do you agree?

Junior: What are comments

Mid-level: Hah! My code is so clean, I don't NEED comments!

Senior: comments comments comments comments comments comments comments comments comments comments comments comments comme-...

The best code review experience I had is when I started with my first job I used to write 10 lines of code and used to get 20 comments on that, well i learnt a lot from him and now whenever i get review comments on my PR i actually feel good.

Code never lies.
Comments sometimes do.

I had high ideals when I started working here. The entire code base was practically devoid of comments. Its been 5 years and it is still practically devoid of comments. I have become like them...

>Hey, my code doesn't work. Can you check why?

There are no comments...

When I started my internship my PRs got absolutely blasted by code style comments and suggestions about code that could be more optimized

Now, almost a year later, I can proudly say my PRs only get a maximum of 2 comments and I've seen myself grow over the months :)

Our team had a brilliant engineer, he made a tool that would convert IBM Assembler code to C, comments included. the comments are the assembler code. bleh

forget comments! write self documenting code that's obvious to anyone reading the system.

i hate myself for having a better idea to write a procedure or a function after getting it done. *comments the first set of code, just to be sure.*

/* Spending time writing comments in code because if everything else fails, at least I can write a novel depicting a deteriorating struggle to make up my mind from them */

Download an open source project and look for code comments to get my understanding... Nothing but 'todos' here and 'todos' there

1. Wrote super complex snippet w/o comments.
2. Commit & push.
3. Read code after 1 month
4. Ask yourself how you wrote that.

They say I have to learn poems to make my memory fresh.

I don't need that! I write code without comments

Shit swizzler in school group project doesn't delete ANY code. Just comments out everything, everywhere.

Some of the files is scrolling through 30 lines of comments, 2 actual lines of code, 20 lines of comments, 5 lines of actual code, ...

Somewhere, in between all of his shit code, I just want to add: "Fucking stop with the comments, you wheezing bag of dicktits"

Oh and this afternoon, he asked me where he could find the Bootstrap code I'd written. He couldn't find 'the file'. I had to explain to him that it's kinda everywhere, throughout the HTML.. As a novice in many many things I fully understand not knowing everything. But the little shitstick told me he 'uses bootstrap all the time' just two hours before he asked me this.

I swear everything this guy touches turns to shit. One more day of this and I'll slap the bitch out of him.

P.S. Free virtual advocado for the first person to guess what movie inspired my insults (easy, I know)

Concentrating and understanding someone's code/ script. :|

The code is not in class form, does not have comments, and indentation is out of control. T_T

Code doesnt work, i dont know why
*comments then uncomments same line*
Code works, stilll dont know why

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

Please //comment ur code!!

Feature request: Being able to copy text from rants/comments on mobile. Also some sort of code formatting would be nice!

Recently graduated and in a job. Had a pull request merged with no comments or changes asked for by the code reviewer today. It's the little victories.

Being forced to rush code, then waiting for merge approval from your US based approver at 3am while they add comments to the review complaining variables aren't final.

When you look into the code of old developers with nice comments such as "What a fucking retard he is trying to book in the past". Just laught .

Post the funniest comments you have found deep in your projects code.

Put as many comments into the code as possible.

Leaving out comments assuming your code is readable enough. Code != English

Today I've ran into a slightly biased comment in our production code...

int i = 0; // i is an integer initialized to 0

wtf?!?!?

comments should explain why not how or what the code is doing...

If you have any project (personal or not, doesn't matter) that does not have proper code comments and documentation and you don't want to make one because of the effort (maybe even "wasted" effort), think again. When commenting on a wall of code to say what it does, you may find a better way of doing what you have to do, possibly increasing performance, or improving security.

I have been able to do better input sanitization for a method on a personal project of mine because of this.
Don't use the amount of effort for proper documentation as an excuse not to make one.

There is more comments in my code . Than actual code !

People be like: “We don’t use comments cause good code should explain itself”

Then proceed to use complicated app architectures with classes all over the place.

Fuck.

Love writing comments, hate writing documentation.

Ugh, I know it is needed but just don't care about it as much as the code/comments which is a more direct 'here is what this does' approach. Writing idiot proof documentation sucks. Any little change? Have to remember to update the docs. Yeah, not happy.

So I fix a bug and I create a PR, someone reviews it and leaves a couple of comments, I address those comments and push up my updated code thinking “great I should be ok to move onto this big story waiting for me”
Then some Expletive.random(); from a totally different team who has no context of my change comes in and starts leaving petty comments. He literally pointed out 3 different things that could be made private/package-private.
Bugger off and focus on your own team’s work instead of leaving comments about relatively trivial things on my PRs.
Apparently he is well known for this. I can tell we are gonna have some fun encounters...

the two code review personality types

review activity:

- dev A: requests code review, sets dev B and dev c (myself) as reviewers

 - dev C comments: this review is marked with a complexity > 9000, touches > 20 files and has zero comments... also there's a lot of refactoring going on, making it hard for me to tell what the actual relevant changes are. can you please add more comments to this review?

 - dev B (10 mins later): approved review

Currently having a stupid fight in my PR comments to remove dead code because I refuse to write a whole book to justify a cleanup commit.

When Google (or other companies) make AI that makes another AI or code does the original AI write comments?

When people use so many special characters to decorate their comments that their code looks like Brainfuck code :|

"Multiline strings can be used as block comments in Python." Except in some places, where your code will pretty much blow up without any errors, because instead of commenting out a portion of an array, you've just added one big string element. And there's no other way to make block comments. And after actually commenting out every single line, your version control won't know how to merge it anymore, because there are now 100 changed lines instead of 2.

If the code and the comments disagree, they both are probably wrong.

At the risk of starting a war, what are folks opinions on in-line comments?

Personally, I'm against them. Self documenting code for the what, SCM for the why.

Comments can get out of date if not maintained; code cannot lie.

Me: I'll comment that later
Also me: Why tf isn't there​ any comment

No seriously, comments and documentations are really necessary. Today I've been debugging for hours, why a certain variable has a certain value. Age of code: 15+ years. No comments. No docs. 🙃

New guy hasn't written or commuted any code, yet he is the most annoying person doing code reviews with bullshit comments.

Normally when I start at a new shop, I hold off on code reviews until I'm at least familiar with the project(s).

I just don't like copy-pasting the code. can I become a good programmer?
please give honest opinions in the comments.

Genuine question, what was the most comments you've left in a single code review?

Just reviewed pull request submitted by a developer working for a contractor company and needed to leave 70 comments. Seventy.

Opened LinkedIn and saw a post from that same developer saying he left the contracting company an hour ago. I still can't believe it.

Comments belong here on devRant, not in your code!

Code cleanly folks.

“Good code is its own best documentation. As you’re about to add a comment, ask yourself, ‘How can I improve the code so that this comment isn’t needed?'”
– Steve McConnell 

Been trying to update some really old C++ piece of code.
And all the comments and variable names are in FR*NCH.
Apparently they didn't had accents in the keyboards back then, because they used stars instead.
Makes it really hard to tell commented code from French comments.

Obs: I don't speak nor can read French. Neither does anyone in my team.

I've finally got into the habit of writing descriptive comments in my code. I've always just got so into the coding and comment later when I don't know what the code does anymore xD

I read the source code of a guy who decided to name his variables, functions, and comments in Spanish which is not a language I'm familiar with. So I need to first translate the code into English and then understand what it does.

Am I the only one who heavily comments their code when learning a new language to the point of you essentially describing what everything is and how everything works

Raise your hand if you don’t trust the comments in code most of the time, and take at least a superficial look at the code block to ensure that it does what it says it does.

If you have any exceptions, please share.

I just hate writing comments and the Software Design Document for the code and changes done my me.

Old but Gold

Code never lies, comments do