Greppability is an underrated code metric

Re:Greppability is an underrated code metric by alexvitkov on Wednesday September 04, 2024 @01:14PM (#41448145)

Wild that the people who made the language that forces me to type

  if err != nil {
      return nil, err
  }

after every second statement are advising against code repetition.

[ Parent | on HN ]

Re:Greppability is an underrated code metric by kiitos on Wednesday September 04, 2024 @04:05PM (#41450128)

Wild that you don't distinguish between error handling and name repetition.

[ Parent | on HN ]

Re:Greppability is an underrated code metric by alexvitkov on Wednesday September 04, 2024 @05:28PM (#41451052)

The issue is about "repetition" - a concept that exists on the syntactic level, and is unavoidable in Go.

To put it in a way you may understand, it's when you have to press keys in the same order a lot of times and you get sad.

[ Parent | on HN ]

Re:Greppability is an underrated code metric by kiitos on Thursday September 05, 2024 @04:29PM (#41460145)

Repetition at the syntactic level, as you describe here, is, statistically, zero percent of the time spent in any meaningful software project. It, quite literally, doesn't matter.

Time spent by authors typing source code characters into their editor is almost entirely irrelevant. The only thing that matters is the time spent by readers parsing and understanding the source code in the VCS.

[ Parent | on HN ]