in reply to Mathias Hasselmann

mastodon - Link to source

daniel:// stenberg://

@taschenorakel there has been some initial work in generalizing the scripts so that's something that might happen: github.com/curl/stats/pull/16

Generalize for any repo by jericson · Pull Request #16 · curl/stats

I love the curl dashboard and I want to use some of the stats for other projects. I forked this repository and started generalizing the scripts. For instance, github-cache.pl grabs a copy of issues...
GitHub
@Mathias Hasselmann
in reply to daniel:// stenberg://

mastodon - Link to source

William Salmon

I don't want to come over too critical as I have a huge amount of appreciation and respect for you & curl.
That said I have found that while having complexity in code is bad, it's also hard to reduce and one way that some people try to reduce it is to "hide" it across many simple looking functions.
I once got my pen and paper out and found that to get from one function at the high level to the low level equivalent the path was through 5 lays of inheritance and 3 different branches
This entry was edited (3 months ago)
in reply to daniel:// stenberg://

mastodon - Link to source

poleguy looking for lost tools

@pointswaves I also had the experience of a developer breaking a long function into four or so shorter functions that called each other in sequence. I'm sure you don't have a high risk of this.
My insight from that experience is that what really matters is that the complexity of the code is as low as possible considering the complexity of the problem. But the complexity metrics do not consider the problem complexity. I would rather see all the code for a complex problem in one place.
@William Salmon
⇧