Subj : Re: Software development book recommendation
To   : tenser
From : Adept
Date : Mon Mar 17 2025 02:09 pm

 te>  BW>  > "Clean Code".  It's bad advice, and my opinion is that Robert
 te>  BW>  > Martin is a blowhard and a charlatan.  He's just not a very
 te>  BW>  > good programmer.
 te>  BW> 
 te>  BW> Come on, tenser - stop beating around the bush and tell us what you
 te>  BW> really think :)
 te> 
 te> Well, in fairness, I don't think he kicks puppies or anything.  :-)

Perhaps there's already something later, but I was hoping there'd be something describing why it's bad advice.

The rest of it I don't particularly care about, since there are plenty of blowhards, charlatans, and bad programmers.

And, heck, most of us probably do those things to some extent from time to time regardless.

Anyway, I haven't read Clean Code, but I'm very pro commenting. Yes, there are such things as too much commenting, but aside from in school when people were commenting, "//adds 1 to x", it's not something I've ever seen.

But random blocks of code where I'm supposed to just _know_ what the heck the previous programmer was supposed to mean, based off of variables? Yeah, those I've seen plenty of.

Especially when it's something where I don't understand the code base, and I'm looking for _anything_ to help me to latch on what's going on in a certain section.

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: Storm BBS (21:2/108)

.