Life is too short to have commented codes; don't want to go back to it once it shows up in the static code analysis scan

But life isn't too short to figure out WHY some piece of code is doing something, or changing it and then finding out something else doesn't work anymore and debugging that stuff, right?

But any inheriting dev will expend his short life figuring out the code

Commented code (during commits) = piece of garbage

@delose Looks like you're high on the "good code doesn't need comments" cool aid. Don't worry, that will wear off once you have to maintain code by devs who drank that cool aid.

I'm ok with code with comments but not commented code 😉

@delose You mean, commit messages that should actually be comments in code?

@Fast-Nop code changes that are commented code - it has nothing to do with commit comments. If you are familiar with Sonarqube, these commented codes are flagged as a code smells which prompts developers to rework and delete that code.

@delose Aahhhhh you mean OUTcommented code! Now I get it and agree, that's what version control is for in the first place.

@Fast-Nop it is like reading clean code and assuming it is the word of god... The worst part of that book is narrow view against comments. I AGREE that code should be as descriptive as possible but well placed comments are life saving.
Note: I fell to same trap, he meant commented out code...