

I think comment ratio could be a fairly misleading metric. There are programs out there that requires a lot of context upfront that distills down to just a few lines of code, and especially those that are more academically interesting.


I think comment ratio could be a fairly misleading metric. There are programs out there that requires a lot of context upfront that distills down to just a few lines of code, and especially those that are more academically interesting.
Please don’t remind me. Had a colleague with a senior title who just vibecoded on our CI pipeline and it ended up blocking deployments for half a day.


AFAIK, the author isn’t anti-proprietary. His goal with the newsletter is to share news that relates to self-hosting, which isn’t limited to FOSS, which is something he mentioned in one of his recent newsletters (it’s a common criticism he gets apparently). And there’s the reality where the vast majority of the source for selfhosted software are hosted on Github.
I don’t claim it to be common practice, just saying that it exists. That said, it may be “niche” in the grand scheme of things, but by no means do I think it’s small and insignificant. If anything, such codebases are typically foundational libraries in the giant stack of cards most other software engineers build.
See also antirez’s article about code comments https://www.antirez.com/news/124 You’ll notice how some of the snippets would’ve easily failed your criteria.