Avoid Else, Return Early (2013)

Re:Avoid Else, Return Early (2013) by macspoofing on Monday March 26, 2018 @12:20PM (#16680007)

Meh. It's noise but what's the harm? It was generated by an IDE so nobody had to physically type that. And usually no developer will be dwelling on this object or this area of the object. It just sits there doing no harm to anyone.

>LOC is more valid as a metric than most care to admit.

It's not.

[ Parent | on HN ]

Re:Avoid Else, Return Early (2013) by loup-vaillant on Monday March 26, 2018 @05:15PM (#16682663)

> It was generated by an IDE

Not all of it, actually.

> nobody had to physically type that

We totally had to read that.

> And usually no developer will be dwelling on this object or this area of the object.

Well… yes, usually. Sometimes however we did want to pay more attention than usual. At that point the original dev would have made a real comment. And that comment was lost in the noise, so you couldn't even distinguish between real comments and useless boilerplate.

[ Parent | on HN ]

Re:Avoid Else, Return Early (2013) by taeric on Monday March 26, 2018 @12:46PM (#16680263)

I seem to recall that LOC correlated just as heavily with bugs and other problems as any other measure it was put up against. And, just like every other measure, gaming it leads to a degenerative case. (Can't remember where I saw this, or I would provide a citation.)

I'll repeat my current gut feeling. Intrinsic measures of software quality are terrible as guides for how to write code. They are decent at predicting quality, but are not usable in a prescriptive way to write quality code.

[ Parent | on HN ]