Skip to content
0:00 / 0:00

#codecomments#cleancode#codeaesthetic

Don't Write Comments

CodeAesthetic

438K subscribers • 4 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

977K views3 years ago2 recommendations

Tools and practiceSoftware designSimplicity and complexityRefactoring and legacy codeTesting

CodeAesthetic explains why inline comments often clutter codebases and argues that developers should write self-documenting code and high-level documentation instead.

Why you shouldn't write comments in your code (write documentation) Access to code examples, discord, song names and more at patreon.com/codeaesthetic References: commitstrip.com/en/2016/08/25/a-very-comprehensive-and-preci…?

Why it's here

2 people recommend this

What people say. Recommended as a great explanation of why code comments should explain why, not how, and why good code is self-explanatory.

u/SnekIrlin r/C_Programming • Recommends

On “i made my first ever c program”

why are you spoiling every line with comments? this is dystopian level code, no need for a comment // now we return true before return true no need for a comment explaining the imports. comments should explain why not how, and good code should be mostly simple to understand without comments. link to this video

u/CutestCuttlefishin r/programming • Recommends

On “Do you comment your code?”

I agree with Code Aestethics on youtube and what he says about commenting code.