Write comments you dumb fucks.

If you change shit that is different from the original pattern， fucking write a comment.

1 minute vs. 45 minutes you mother fucker.

This is my favorite rant ever.

Saw another rant about someone complaining about too many comments.. I'd rather have too many than not enough

Git blame?

@electrineer na the dude left the company.

Every one in the company knows who it is.

@Santaclauze and what's in the commit message? "fix"?

@electrineer “bug fix”

@Santaclauze 🤦‍♂️

Can't stand those people. if you can't document you're either lazy or hiding something. Either way I don't want them on my team.

Do you have an actual example of where you think there should be a comment?

We once had a git commit on master branch which contained lines that break whole website. It was outsource guy who wrote comment like "DO NOT DELETE THESE LINES. SKYPE ME FOR EXPLANATION randomguy666". And yes, we give access to master, our workflow is shit.

I learned to write understandable code and write as few comments as needed. Code quality and -readability is much better than some obvious and unnecessary comments

Don't just write comments but also write them for humans not aliens, I have seen comments like
//abc is equals to 0
if(abc == 0)

You fucking dumb shit I can read code, Whats the point of translating code ?

@wholl0p agree but the logic should be nicely formatted with a one liner comment to describe it.
20sec vs 5-10 mins :)

I wrote a comment as you asked. Ya happy now?

(cuz this.comment==true)