From b2a7c592bd35d7eb529cf163a8470362f7c3126c Mon Sep 17 00:00:00 2001 From: "openshift-merge-bot[bot]" Date: Fri, 20 Dec 2024 12:27:12 +0000 Subject: [PATCH] deploy: 3b66f18f0efe91073593ae442a4d9a545786c4dd --- blog/Understanding-Cyclomatic-Complexity/index.html | 2 +- blog/grafana-on-openshift-for-kuadrant/index.html | 4 ++-- blog/index.html | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/blog/Understanding-Cyclomatic-Complexity/index.html b/blog/Understanding-Cyclomatic-Complexity/index.html index d37da27..74940f5 100644 --- a/blog/Understanding-Cyclomatic-Complexity/index.html +++ b/blog/Understanding-Cyclomatic-Complexity/index.html @@ -159,7 +159,7 @@

Co

Tracking the metric over time is worthless, as the project grows, so does the cyclomatic complexity and therefore the metric. Where the over time metric can be used is a reminder to existing developers of how much more complex the project is of new developer's starting. The onboard time for a new developer will take longer, and any existing developers may require more patience with the new developer. Tracking the Ranks proportional over time may have some benefit in identifying when a project is starting to slip and get "untidy".

Overall, it is a nice metric, just like code coverage, it is a bit meaningless but can help drive decisions on a case by case bases. For public facing APIs, it can help identify areas that many be too broad requiring a developer to hold more context than is required to use the API.

-